AdminException: ADMU3060E: Timed out waiting for server shutdown

[Neeraj Sidhaye]

stopserver WebSphere_Portal

ADMU0116I: Tool information is being logged in file D:\IBM Portal\Portal
server\wp_profile\logs\WebSphere_Portal\stopServer.log
ADMU0128I: Starting tool with the wp_profile profile
ADMU3100I: Reading configuration for server: WebSphere_Portal
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU3111E: Server stop requested but failed to complete.

ADMU0111E: Program exiting with error:
com.ibm.websphere.management.exception.AdminException: ADMU3060E:
Timed out waiting for server shutdown.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file: D:\IBM Portal\Portal
server\wp_profile\logs\WebSphere_Portal\stopServer.log

I googled the problem and found that "PK16700" resolves this problem and this intrim fix available at,
http://www-01.ibm.com/support/docview.wss?uid=swg21238771

but this seems to be from portal 6.0.

I am using portal 6.1, so can any one point me where i can download the same fix for portal 6.1 ?

many thanks..

[ff...@us.ibm.com]

How did you stop the server? From the command line, or Windows services, or Portal configengine command?
You may want to increase SOAP request timeout in soap.client.props from defautl 180 to 6000.
If you are on Linux, you may want to check "ulimit -n" and increase the default values, if they are small. It's recommended to set it to something like 10240.

-FF

The postings on this site are my own and do not necessarily represent the positions, strategies or opinions of IBM.

[jwi...@us.ibm.com]

The APAR you reference is for a relatively old version of WebSphere Application Server (WAS). It should be included in the WAS that ships with Portal 6.1, so this likely is not the problem.

Since you are running stopserver from a Windows command line, first increase the timeout using the -timeout parameter, as described in the WAS InfoCenter:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_stopserver.html

How quickly does this fail now? You might need to try 30 minutes or 1 hour (timeout is in seconds) just to make sure there are no hung threads, just slow performance. If it does not complete in an hour, a thread is probably hung and you should open a PMR with support to determine which thread hangs and why.

If this is a development environment, you might consider running enable-develop-mode-startup-performance to improve startup/shutdown performance (disables all but the core 13 applications Portal needs to run). This would not be recommended for production.

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/install/inst_opt.html

[Neeraj Sidhaye]

All , thanks for your response.

it's my develpoment env and when i increased the time out, problem solved.
thanks much..

One more question, as seen in second reply
"enable-develop-mode-startup-performance ", i read the infocenter and it says you have to perform this just after the portal installation.
That time i didn't perform this step, can i do it now and if yes how ?

again thanks much for this wonderful info..

[jwi...@us.ibm.com]

I think you should still be able to run the task, although you could encounter problems if you're already using any of the applications disabled by this task. This technote outlines one example:

http://www.ibm.com/support/docview.wss?rs=688&ca=portall2&uid=swg21381788

So, if you're interested in running this task to improve startup/shutdown performance, then consider which applications are already in use. Of course, if you do not have very many startups/shutdowns then you could just bump up the timeout and leave all the applications running.