WebSphere Application Server - Re: Error stopping server in WAS 6.0.2.7: ADMU3060E: Timed out waiting for server shut

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > March 2006 > Re: Error stopping server in WAS 6.0.2.7: ADMU3060E: Timed out waiting for server shut





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Error stopping server in WAS 6.0.2.7: ADMU3060E: Timed out waiting for server shut
Stephen Cocks

2006-03-15, 7:50 am

Can you tell from the SystemOut.log for the server whether the request to
shutdown is being received? And if it is then does the server actually
shutdown but just take a long time (in which case increasing the timeout is
all that's required)... or perhaps the shutdown processing starts but
"hangs" at some point?

--
Stephen Cocks
ESB System Management

"Terrance Grahn" <tjgrahn@gmail.com> wrote in message
news:dv4m3t$7004s$1@news.boulder.ibm.com...
> Not just my computer but it seems all computers (5) are hanging when
> trying to stop the server via 'stopserver.bat' in the shortcut created by
> WAS in the start menu. Using the -trace option, I get the following
> output. Could someone point me in the right direction?
>
> thanks in advance,
> Terrance
>
> ....
> [3/13/06 14:48:12:338 CST] 0000000a AdminTool A ADMU3111E: Server
> stop requested but failed to complete.
> [3/13/06 14:48:12:338 CST] 0000000a WsServerStop E ADMU3002E: Exception
> attempting to process server server1
> [3/13/06 14:48:12:338 CST] 0000000a WsServerStop E ADMU3007E: Exception
> com.ibm.websphere.management.exception.AdminException: ADMU3060E: Timed
> out waiting for server shutdown.
> [3/13/06 14:48:12:338 CST] 0000000a WsServerStop A ADMU3007E: Exception
> com.ibm.websphere.management.exception.AdminException: ADMU3060E: Timed
> out waiting for server shutdown.
> at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:338)
> at
> com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:226)
> at
> com.ibm.ws.management.tools.WsServerController. executeUtilityOnWindows(WsServerControll
er.java:131)
> at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> at java.lang.reflect.Method.invoke(Method.java:391)
> at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
> at java.lang.Thread.run(Thread.java:568)
>
> [3/13/06 14:48:12:348 CST] 0000000a AdminTool E ADMU0111E: Program
> exiting with error: com.ibm.websphere.management.exception.AdminException:
> ADMU3060E: Timed out waiting for server shutdown.
> at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:338)
> at
> com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:226)
> at
> com.ibm.ws.management.tools.WsServerController. executeUtilityOnWindows(WsServerControll
er.java:131)
> at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> at java.lang.reflect.Method.invoke(Method.java:391)
> at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
> at java.lang.Thread.run(Thread.java:568)
>
> [3/13/06 14:48:12:348 CST] 0000000a AdminTool A ADMU0111E: Program
> exiting with error: com.ibm.websphere.management.exception.AdminException:
> ADMU3060E: Timed out waiting for server shutdown.
> at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:338)
> at
> com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:226)
> at
> com.ibm.ws.management.tools.WsServerController. executeUtilityOnWindows(WsServerControll
er.java:131)
> at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> at java.lang.reflect.Method.invoke(Method.java:391)
> at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
> at java.lang.Thread.run(Thread.java:568)
>
> [3/13/06 14:48:12:348 CST] 0000000a AdminTool 3 Returning from
> auxiliary method issueMessage with return code: 111
> [3/13/06 14:48:12:348 CST] 0000000a AdminTool A ADMU0211I: Error
> details may be seen in the file: C:\Program
> Files\IBM\WebSphere\AppServer/profiles/default\logs\server1\stopServer.log
> [3/13/06 14:48:12:348 CST] 0000000a AdminTool 3 Returning from
> auxiliary method issueMessage with return code: 211
> [3/13/06 14:48:12:348 CST] 0000000a AdminTool 3 Returning from
> executeUtility method with return code: -1
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com