CLM 6.0.4 starting application "hung" after migration

Milan Krivic

(980●13●176●143) edited

Sep 15 '17, 9:48 a.m.

Hi,

we are in the process of migrating CLM 6.0.1 to CLM 6.0.4 and also moving from Win Server 2008 to Win Server 2012.

We deployed ccm, qm and jts applications, but they "hung" up while starting, and they can not be started.

We are using Websphere Application SErver 8.5.5.6 and DB2 WSE 10.5.0.5.

here is the system out log:

[15.09.17. 11:43:49:491 CEST] 00000060 ThreadMonitor W WSVR0605W: Thread "server.startup : 1" (0000004d) has been active for 712126 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.

at sun.misc.Unsafe.park(Native Method)

at java.util.concurrent.locks.LockSupport.park(LockSupport.java:182)

at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:822)

at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:980)

at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1292)

at java.util.concurrent.Semaphore.acquire(Semaphore.java:297)

at com.ibm.team.repository.server.servletbridge.ContextNameCallback.waitForProvisionCompleteSignal(ContextNameCallback.java:62)

at com.ibm.team.repository.server.servletbridge.JazzServlet.init(JazzServlet.java:52)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:342)

at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:1366)

at com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions(WebApp.java:627)

at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:593)

at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:422)

at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)

at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169)

at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749)

at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634)

at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:426)

at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:718)

at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1177)

at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1370)

at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639)

at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:968)

at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:776)

at com.ibm.ws.runtime.component.ApplicationMgrImpl$5.run(ApplicationMgrImpl.java:2195)

at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5477)

at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5603)

at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)

at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2200)

at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:435)

at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)

at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:378)

at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:126)

at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:984)

at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:502)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)

[15.09.17. 11:43:49:491 CEST] 00000060 ThreadMonitor W WSVR0605W: Thread "server.startup : 0" (0000004c) has been active for 711423 milliseconds and may be hung. There is/are 2 thread(s) in total in the server that may be hung.