SAP Knowledge Base Article - Preview

1552147 - Java Node Hanging Starting apps, ConfigurationManager.


  • Java nodes remain in state Starting framework  
  • Status of node(s) does not change over time  
           Loading: LogManager ... 297 ms. 
           Loading: PoolManager ... 0 ms.  
           Loading: ApplicationThreadManager ... 62 ms.  
           Loading: ThreadManager ... 16 ms.  
           Loading: IpVerificationManager ... 0 ms. 
           Loading: ClassLoaderManager ... 14 ms. 
           Loading: ClusterManager ... 141 ms.  
           Loading: LockingManager ... 78 ms.
           Loading: ConfigurationManager ...                                                  

Thread Dumps show a stack trace similar to the one seen below:

"Thread-1" tid=0x6000000000ca8290 nid=0x31 prio=7 in Object.wait()
 at java.lang.Object.wait(Native Method)
 - locked<0x9ffffffeda344098> (a
 - locked<0x9ffffffed9af13f0> (a
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 at java.lang.reflect.Method.invoke(

Note: There is little or no other activity in the Thread Dump     



  • SAP NetWeaver 7.0
  • SAP NetWeaver 2004


SAP NetWeaver 2004 ; SAP NetWeaver 7.0


Starting framework, Loading: ConfigurationManager, Configuration, Manager, ConfigurationCache, Configuration, Cache, Hang, Enqueue, server, Central services , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-CST-EQ , Enqueue , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.