WebSphere AS Windows Service Not Stopping
damien....@dva.gov.au
I have a Windows Server 2003 with WebSphere AS ND 6.0.2.17 installed. I have used "wasservice" to add WAS as a Windows Service.
WAS starts fine using the Windows Service. However, when I try to stop the Windows Service, I only get the following in SystemOut.log:
[25/09/07 11:52:32:725 EST] 0000003f AdminHelper A ADMN1021I: An attempt is made to stop the TheCuramServer server.
WAS never stops, and never writes any more information. If I try to stop WAS using the command line, I get the following:
E:\IBM\WebSphere\AppServer\bin>stopserver TheCuramServer
ADMU7702I: Because TheCuramServer is registered to run as a Windows Service,
the request to stop this server will be completed by stopping the
associated Windows Service.
java.lang.reflect.InvocationTargetException
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(DelegatingMethodAcces
sorImpl.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:570)
Caused by: com.ibm.websphere.management.exception.AdminException: ADMU7705E: Fai
led while trying to stop the Windows Service associated with server: TheCuramSer
ver;
probable error executing WASService.exe: com.ibm.ws.management.tools.ProblemInWA
SServiceException: ADMU7711E: Unexpected exception associated with WASService.ex
e: exitCode = -1 during processing of server with name: TheCuramServer
at com.ibm.ws.management.tools.WindowsService.doWASServiceAction(Windows
Service.java:382)
at com.ibm.ws.management.tools.WsServerStop.execWithWinService(WsServerS
top.java:143)
at com.ibm.ws.management.tools.WsServerController.executeUtilityOnWindow
s(WsServerController.java:128)
at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:104)
... 7 more
ADMU0116I: Tool information is being logged in file
E:\IBM\WebSphere\AppServer\profiles\default\logs\TheCuramServer\start
Server.log
ADMU0128I: Starting tool with the default profile
ADMU3100I: Reading configuration for server: TheCuramServer
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server TheCuramServer open for e-business; process id is 6132
ADMU0116I: Tool information is being logged in file
E:\IBM\WebSphere\AppServer\profiles\default\logs\TheCuramServer\stopS
erver.log
ADMU0128I: Starting tool with the default profile
ADMU3100I: Reading configuration for server: TheCuramServer
ADMU3201I: Server stop request issued. Waiting for stop status.
And nothing more. Anyone have any ideas?
Thanks, -Damien
Paul Ilechko
>
> And nothing more. Anyone have any ideas?
>
Well, I would recommend not running it as a service. Start and stop it
from the command line.
damien....@dva.gov.au
E:\IBM\WebSphere\AppServer\bin>stopserver TheCuramServer -trace
ADMU0115I: Trace mode is on.
ADMU0116I: Tool information is being logged in file
E:\IBM\WebSphere\AppServer\profiles\default\logs\TheCuramServer\stopS
erver.log
ADMU0128I: Starting tool with the default profile
ADMU3100I: Reading configuration for server: TheCuramServer
ADMU3201I: Server stop request issued. Waiting for stop status.
I see one entry in the SystemOut.log:
[25/09/07 12:57:08:778 EST] 0000003b AdminHelper A ADMN1021I: An attempt is made to stop the TheCuramServer server.
But nothing more. The server just won't stop! Any ideas?
damien....@dva.gov.au
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.
ADMU0211I: Error details may be seen in the file:
E:\IBM\WebSphere\AppServer\profiles\default\logs\TheCuramServer\stopS
erver.log
The stopServer.log says:
[25/09/07 13:17:08:840 EST] 0000000a AdminTool A ADMU3111E: Server stop requested but failed to complete.
[25/09/07 13:17:08:855 EST] 0000000a WsServerStop E ADMU3002E: Exception attempting to process server TheCuramServer
[25/09/07 13:17:08:855 EST] 0000000a WsServerStop E ADMU3007E: Exception com.ibm.websphere.management.exception.AdminException: ADMU3060E: Timed out waiting for server shutdown.
[25/09/07 13:17:08:855 EST] 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(WsServerController.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:570)
[25/09/07 13:17:08:855 EST] 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(WsServerController.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:570)
[25/09/07 13:17:08:855 EST] 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(WsServerController.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:570)
[25/09/07 13:17:08:855 EST] 0000000a AdminTool 3 Returning from auxiliary method issueMessage with return code: 111
[25/09/07 13:17:08:871 EST] 0000000a AdminTool A ADMU0211I: Error details may be seen in the file: E:\IBM\WebSphere\AppServer\profiles\default\logs\TheCuramServer\stopServer.log
[25/09/07 13:17:08:871 EST] 0000000a AdminTool 3 Returning from auxiliary method issueMessage with return code: 211
[25/09/07 13:17:08:871 EST] 0000000a AdminTool 3 Returning from executeUtility method with return code: -1
From a reasonable amount of Googling, it looks like there's a few people that have had this problem, but no resolution ... please help!
Mark Lewis
something like this:
wsadmin -c "$AdminControl stopServer TheCuramServer"
I'm not sure why the normal methods for stopping the server are not
working.
Hope that helps,
Mark.
fen...@gmail.com
> Lots of logs
How about this:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK14391
damien....@dva.gov.au
I tried using wsadmin as you suggested, but with the same result. It's as if the Application Server recognises that it has received a request to stop, but then just ignores the request.
Does anyone know what WAS waits for when it receives a stop request? Does it service running threads before shutting down, or does it kill the threads?
Thanks,
Damien
Yuriy Petrov
1. Before making the attempt to stop the server, open admin console and (a) enable tracing (b) and
set the _runtime_ tracing level to the maximum.
2. Try to stop the server
3. Watch the trace.log file. The file will be probably _very_ big, so you will need all your
patience to walk through the file carefully in hope to get any clues why the server hangs at
shutdown process. Most likely the file will grow, so if you use some text editor in this
investigation to view the file, then you should reload the file time to time. Obviously, the most
"tasty" information should be at the end.
Ben_
logRoot, wasHome, logFile).
Search on the support site for documentation or problems with keywords like
wasservice, logroot and other arguments.
bshah
Thanks
bshah
damien....@dva.gov.au
[27/09/07 15:26:38:830 EST] 0000004d SOAPResponse 3 the generated soap response envelop is
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Header xmlns:ns0="admin" ns0:ProcessVersion="awsd54Cell:awsd54:TheCuramServer:6.0.2.17" ns0:WASRemoteRuntimeVersion="6.0.2.17" ns0:JMXMessageVersion="1.2.0" ns0:JMXVersion="1.2.0">
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:invokeResponse xmlns:ns1="urn:AdminService" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<return xsi:type="xsd:anyType" xsi:nil="true"/>
</ns1:invokeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I'm lost. I might just rebuild the server. Any final ideas?
Yuriy Petrov
> I turned tracing on maximum, as you recommended, and tried to stop the server using "stopServer.bat AppServerName". I can see the "stop request" received by the server, then the server prints a message saying the "stop request" has been received. Then it sends the following response to the client, but doesn't appear to do anything else. The only further messages after this SOAPResponse are alarms and binaryheap messages.
Second - "...alarms and binaryheap messages" - what's that? Can you give some examples of those log
entries?
damien....@dva.gov.au
Yes, "*=all"
> "...alarms and binaryheap messages" - what's that?
I don't know :) Here's some examples:
[27/09/07 15:26:44:064 EST] 0000005a BinaryHeap > minimum Entry
[27/09/07 15:26:44:064 EST] 0000005a BinaryHeap < minimum Exit
[27/09/07 15:26:44:064 EST] 0000005a BinaryHeap > deleteMin Entry
[27/09/07 15:26:44:064 EST] 0000005a BinaryHeap > heapify, heapSize: Entry
41
[27/09/07 15:26:44:064 EST] 0000005a BinaryHeap < heapify Exit
[27/09/07 15:26:44:064 EST] 0000005a BinaryHeap < deleteMin Exit
[27/09/07 15:26:44:064 EST] 0000005a AlarmThreadPo > firing alarm Entry
_Alarm(1190870804049,com.ibm.ws.timeutils.QuickApproxTimeA@6d471c58,null)
[27/09/07 15:26:44:064 EST] 00000032 AlarmManager > createDeferrable Entry
1000
com.ibm.ws.timeutils.QuickApproxTimeA@6d471c58
<null>
[27/09/07 15:26:44:064 EST] 00000032 BinaryHeap > insert Entry
_Alarm(1190870805064,com.ibm.ws.timeutils.QuickApproxTimeA@6d471c58,null)
[27/09/07 15:26:44:064 EST] 00000032 BinaryHeap < insert Exit
[27/09/07 15:26:44:064 EST] 00000032 BinaryHeap > minimum Entry
[27/09/07 15:26:44:064 EST] 00000032 BinaryHeap < minimum Exit
[27/09/07 15:26:44:064 EST] 00000032 AlarmManager < createDeferrable Exit
_Alarm(1190870805064,com.ibm.ws.timeutils.QuickApproxTimeA@6d471c58,null)
[27/09/07 15:26:44:064 EST] 0000005a AlarmThreadPo < alarm fired Exit
[27/09/07 15:26:44:064 EST] 0000005a BinaryHeap > minimum Entry
[27/09/07 15:26:44:064 EST] 0000005a BinaryHeap < minimum Exit
[27/09/07 15:26:44:064 EST] 0000005a AlarmManagerT 3 Alarm manager thread waiting
110
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap > minimum Entry
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap < minimum Exit
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap > deleteMin Entry
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap > heapify, heapSize: Entry
15
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap < heapify Exit
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap < deleteMin Exit
[27/09/07 15:26:44:096 EST] 00000058 AlarmThreadPo > firing alarm Entry
_Alarm(1190870804096,com.ibm.ws.cache.BatchUpdateDaemon@7463dc5f,null)
[27/09/07 15:26:44:096 EST] 00000058 AlarmThreadPo < alarm fired Exit
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap > minimum Entry
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap < minimum Exit
[27/09/07 15:26:44:096 EST] 00000058 AlarmManagerT 3 Alarm manager thread waiting
1671
[27/09/07 15:26:44:096 EST] 00000054 AlarmManager > createNonDeferrable Entry
1000
com.ibm.ws.cache.BatchUpdateDaemon@7463dc5f
<null>
[27/09/07 15:26:44:096 EST] 00000054 BinaryHeap > insert Entry
_Alarm(1190870805096,com.ibm.ws.cache.BatchUpdateDaemon@7463dc5f,null)
[27/09/07 15:26:44:096 EST] 00000054 BinaryHeap < insert Exit
[27/09/07 15:26:44:096 EST] 00000054 BinaryHeap > minimum Entry
[27/09/07 15:26:44:096 EST] 00000054 BinaryHeap < minimum Exit
[27/09/07 15:26:44:096 EST] 00000054 AlarmManager < createNonDeferrable Exit
_Alarm(1190870805096,com.ibm.ws.cache.BatchUpdateDaemon@7463dc5f,null)
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap > minimum Entry
[27/09/07 15:26:44:096 EST] 00000058 BinaryHeap < minimum Exit
[27/09/07 15:26:44:096 EST] 00000058 AlarmManagerT 3 Alarm manager thread waiting
1000
Yuriy Petrov
WorkManager which is the subsystem that provides to developers the ability to create and use threads.
Then another hypothesis is: some app gets the thread[-s] from WorkManager and uses it to perform
some app specific task. Because of some reasons, the app's code that is executed within the thread
provided by WAS just can not politely stop its work when the server goes down.
So the questions are:
do you have any applications different from the default ones (i.e. the ones that are deployed on the
server when you install WAS) installed and running on this unstoppable server?
if you do have, then can you stop these apps?
if you do have, then can you connect some debugger to the server's JVM to watch the threads and
forcibly stop the one[-s] that seem good candidates to the bad boys?
if you do have, then can you uninstall these apps and then try to stop the server?
chris.m...@ovations.co.za
We are having the exact same issue with the same version of WebSphere.
What we have noticed is that this error only occurs if we enable Global Security and restart WebSphere. The only problem is then no security is enabled and not an option for our client.
If anyone has any fixes for this please let us know.
thanks
Chris
Juanma Martinez
That sounds as you both need to open a PMR with IBM so it can be
properly investigated and fixes provided if needed.
mark simko
"Juanma Martinez" <juanma_...@es.ibm.com> wrote in message
news:fdjis8$3900q$1...@news.boulder.ibm.com...
What I have found when running Websphere with global security enabled is
that whatever method used to stop the process must be running as the user
you defined when security was enabled.
In other words, if the ID 'WASADMIN' was used to enable global security,
then this ID (WASADMIN) needs to be used to shut down the WAS process. If
you are running in Windows the Websphere service needs to be running under
this ID (WASADMIN). If you are stopping the service from a command line
using the stopServer.bat or .sh file, you need to edit this file and supply
the userID (WASADMIN) and password.
damien....@dva.gov.au
1. Uninstall WebSphere
2. Install WebSphere
Thanks for the posts, people.
D