cancel
Showing results for 
Search instead for 
Did you mean: 

Java Control framework doesn't start

Former Member
0 Kudos

Dear All,

we built new system (Dual stack system) using the system copy method, all the services were up and running fine.

now I am facing an issue in starting up the Java control frame work(JCF), below are the logs for your reference.

JCF stuck at locking manager service as below ::

<sid>adm> tail -10 std_server0.out

SAP J2EE Engine Version 7.01 PatchLevel 97888. is starting...

Loading: LogManager ... 646 ms.

Loading: PoolManager ... 6 ms.

Loading: ApplicationThreadManager ... 94 ms.

Loading: ThreadManager ... 25 ms.

Loading: IpVerificationManager ... 12 ms.

Loading: ClassLoaderManager ... 23 ms.

Loading: ClusterManager ... 299 ms.

Loading: LockingManager ...

and I check the default trace log and its ended as below.

<sid>adm> tail -20 defaultTrace.0.trc

#1.#00144FC2E5A800010000000300002E050004AC7F931DEBCE#1315563835878#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###ReadRunnable: failed to connect to server 1 times, trying to reconnect...#

#1.#00144FC2E5A800000000000C00002E050004AC7F931DEDD5#1315563835878#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###EnccliMultiplex: wakeup to notify connect failure or timeout (#

Would someone plese help in troubleshooting this issue. I checked the memory parameters values (Configtool) and maintained same as the Source system values and the boot strap is fine.

Thanks & Regards

Rajesh Meda

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Issue got resolved after adjusting the memory parameters

Thanks & Regards

Rajesh Meda