search

WASdev / ci.docker.websphere-traditional

Dockerfiles for WebSphere Application Server traditional
Apache License 2.0
171 stars 192 forks source link

script createProfileAndStartServer.sh not working #35

Closed jdluna closed 7 years ago

jdluna commented 8 years ago

Greetings, running the image as specified but when seeing the logs (docker command as specified). There is no activity after 9 to 10 minutes. I'm running the dockerfiles in docker for mac

davidcurrie commented 8 years ago

Hi @jdluna - can you provide more detail about exactly what you have done/are trying to do? Are you building your own images (you mention Dockerfiles) or using one of the images from Docker Hub?

jdluna commented 8 years ago

Greetings @davidcurrie I was using the same Dockerfiles in the developer folder and trying to create the images from the build commands as specified, but when I use the Dockerfile.install have the problem that takes too long to run the script mentioned in the container. I am using Docker for mac and have the repo clone in a local directory.

davidcurrie commented 8 years ago

OK - so you have built your own image. What do you see in the logs when you run it? The script is not meant to terminate but starts the server and then waits for it to terminate (so that the container continues to run). I don't have access to Docker for Mac at work but I can try at home this evening. There is a lot of file I/O during profile creation which I can believe might be slow on Docker for Mac. Out of interest, is there any reason that you are not using the image from Docker Hub?

jdluna commented 8 years ago

@davidcurrie I was trying to see and work with the elements involved in the build of the image, in my particular case, I want to add an mq server installation in the same image as Websphere Application Server (because I had a project that uses this topology). I tried the image from Docker Hub, but as individual images. I know I can compose them, but as for the topology I'm trying to build. I was trying build the image myself but in my mac got these extrange behavior. I know that the administrative task on WAS take like 4 to 5 minutes (in Virtualized Servers) that's why I was trying to achieve

davidcurrie commented 8 years ago

Did you know that the ibmcom/mq image has now been republished? Using the two images from Docker Hub would certainly be less work from a setup/install perspective!

I'm currently in the process of modifying the install process but, using the ibmcom/websphere-traditional:install image on Docker Hub that is built using those same Dockerfiles, I see it get to "open for e-business" in a little under two minutes under Docker for Mac with the time split between profile creation and startup. The contents of my Docker logs (with timestamps) are as follows:

016-08-08T20:06:55.237174310Z Creating profile .................... 2016-08-08T20:07:41.671410210Z INSTCONFSUCCESS: Success: Profile AppSrv01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThisProfile.txt for more information about this profile. 2016-08-08T20:08:00.184011310Z Starting server ................... 2016-08-08T20:08:17.771650110Z ADMU0116I: Tool information is being logged in file 2016-08-08T20:08:17.771917210Z /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log 2016-08-08T20:08:19.139564110Z ADMU0128I: Starting tool with the AppSrv01 profile 2016-08-08T20:08:19.146158410Z ADMU3100I: Reading configuration for server: server1 2016-08-08T20:08:22.476252110Z ADMU3200I: Server launched. Waiting for initialization status. 2016-08-08T20:08:46.709151510Z ADMU3000I: Server server1 open for e-business; process id is 717

How do those compare with what you are seeing?

davidcurrie commented 8 years ago

@jdluna - can we close this issue now?

davidcurrie commented 7 years ago

Please re-open if you're still having issues here.