WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

WebSphere JVM hangs while stopping, due to which stopServer.sh gets timed out.

  • 1.  WebSphere JVM hangs while stopping, due to which stopServer.sh gets timed out.

    Posted Thu January 14, 2016 01:01 AM

    While stopping the JVM using stopServer.sh, getting below errors in stopServer.log -

     

    [1/13/16 21:20:22:093 CST] 00000001 AdminTool     A   ADMU3111E: Server stop requested but failed to complete.
    [1/13/16 21:20:22:095 CST] 00000001 WsServerStop  E   ADMU3002E: Exception attempting to process server c0xadb0
    [1/13/16 21:20:22:096 CST] 00000001 WsServerStop  E   ADMU3007E: Exception com.ibm.websphere.management.exception.AdminException: ADMU3060E: Timed out waiting for serve
    r shutdown.
    [1/13/16 21:20:22:096 CST] 00000001 WsServerStop  A   ADMU3007E: Exception com.ibm.websphere.management.exception.AdminException: ADMU3060E: Timed out waiting for serve
    r shutdown.
            at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:433)
            at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:269)
            at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:112)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
            at java.lang.reflect.Method.invoke(Method.java:620)
            at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)
            at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)
            at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
            at java.lang.reflect.Method.invoke(Method.java:620)
            at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
            at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
            at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
            at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
            at java.lang.reflect.Method.invoke(Method.java:620)
            at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
            at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
            at org.eclipse.core.launcher.Main.run(Main.java:981)
            at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:398)
            at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:161)

     

    There are no errors as such in SystemOut.log. The logging in SystemOut.log gets stopped at a particular step (which is not the same all the time). I have attached the thread dumps taken while stopping the JVM. I analyzed them but didn't find any deadlocked threads, which may be responsible the issue.

     

    Regards,

    Tejas



  • 2.  RE: WebSphere JVM hangs while stopping, due to which stopServer.sh gets timed out.

    Posted Thu January 14, 2016 10:11 AM

    Hi Tejas,

      As brian suggests

      https://www.ibm.com/developerworks/community/forums/html/topic?id=c048b968-7d57-4536-b80e-7c547236ed6c&ps=100

      please collect the data requiered in

      MustGather: Application Server, dmgr, and nodeagent start and stop problems

      http://www-01.ibm.com/support/docview.wss?uid=swg21201014#show-hide

    or at least put the SystemOut.log not the stopserver.log

      Hope this helps. Tell us if you need more support

    Regards



Related Content