Skip to Content
0
Former Member
Jan 02, 2007 at 09:57 PM

Java Copy Dispatcher is not coming up Servers and SDM is fine.

34 Views

Hi All,

I have performed a Java copy os Portal server ep 6.0 sp 17 . Server and SDM nodes are comming up fine but Dispatcher is not coming up and shows the following Errors in

dev_dispatcher log

**********************************************************************

[Thr 772] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************

JHVM_BuildArgumentList: main method arguments of node [dispatcher]

**********************************************************************

[Thr 3086] Tue Jan 2 12:08:08 2007

[Thr 3086] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 3086] JLaunchISetClusterId: set cluster id 3686100

[Thr 3086] Tue Jan 2 12:08:09 2007

[Thr 3086] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 3086] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

[Thr 13110] Tue Jan 2 12:08:19 2007

[Thr 13110] JLaunchISetTelnetPort: set telnet port 50008

[Thr 13110] JLaunchISetTelnetPort: set telnet port 50008

[Thr 15423] Tue Jan 2 12:08:24 2007

[Thr 15423] JLaunchIExitJava: exit hook is called (rc=666)

[Thr 15423] SigISetIgnoreAction : SIG_IGN for signal 20

[Thr 15423] JLaunchCloseProgram: good bye (exitcode=666)

std_dispatcher Error log:

Service classload started. (3 ms).

Service jmx started. (965 ms).

Jan 2, 2007 12:08:21 PM com.sap.engine.services.ssl [SAPEngine_System_Thread[impl:6]_39] Fatal: Source: ; Description: SSL transport supplier registered; Consequences: <event>; Countermeasures:<event>

<AF[1]: Allocation Failure. need 168630824 bytes, 0 ms since last AF>

<AF[1]: managing allocation failure, action=2 (68199536/176159232)>

<GC(1): freeing class com.sap.engine.services.rmi_p4.server.P4ServerObjectInfo(7000000153861d8)>

<GC(1): unloaded and freed 1 class>

<GC(1): GC cycle started Tue Jan 2 12:08:22 2007

<GC(1): freed 95768096 bytes, 93% free (163967632/176159232), in 167 ms>

<GC(1): mark: 29 ms, sweep: 7 ms, compact: 131 ms>

<GC(1): refs: soft 0 (age >= 32), weak 0, final 476, phantom 0>

<GC(1): moved 118396 objects, 9887624 bytes, reason=1, used 3184 more bytes>

<AF[1]: managing allocation failure, action=3 (163967632/176159232)>

<AF[1]: managing allocation failure, action=4 (163967632/176159232)>

<AF[1]: clearing all remaining soft refs>

<GC(2): GC cycle started Tue Jan 2 12:08:22 2007

<GC(2): freed 709488 bytes, 93% free (164677120/176159232), in 120 ms>

<GC(2): mark: 19 ms, sweep: 5 ms, compact: 96 ms>

<GC(2): refs: soft 321 (age >= 32), weak 0, final 5, phantom 0>

<GC(2): moved 103588 objects, 7927136 bytes, reason=1>

<AF[1]: managing allocation failure, action=6 (164677120/176159232)>

JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.

JVMDG315: JVM Requesting Heap dump file

JVMDG318: Heap dump file written to /usr/sap/EPR/JC00/j2ee/cluster/dispatcher/heapdump954532.1167768502.phd

JVMDG303: JVM Requesting Java core file

JVMDG304: Java core file written to /usr/sap/EPR/JC00/j2ee/cluster/dispatcher/javacore954532.1167768503.txt

JVMDG274: Dump Handler has Processed OutOfMemory.

<AF[1]: Insufficient space in Javaheap to satisfy allocation request>

<AF[1]: completed in 2109 ms>

FATAL: Caught OutOfMemoryError! Node will exit with exit code 666java.lang.OutOfMemoryError: JVMXE006:OutOfMemoryError, stAllocArray for executeJava failed

at com.sap.engine.core.pool.impl1.PoolManagerImpl.get(PoolManagerImpl.java:97)

at com.sap.engine.core.manipulator.ClientDataImpl.ensureDataSize(ClientDataImpl.java:110)

at com.sap.engine.core.manipulator.TCPRunnableConnection.ensureInDataSize(TCPRunnableConnection.java:590)

at com.sap.engine.core.manipulator.TCPRunnableConnection.sleepRead(TCPRunnableConnection.java:864)

at com.sap.engine.core.manipulator.TCPRunnableConnection.access$700(TCPRunnableConnection.java:26)

at com.sap.engine.core.manipulator.TCPRunnableConnection$NonHttpThread.run(TCPRunnableConnection.java:1347)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

I would appreciate if anyone can help in resolving this issue. All suggestions are welcome ..

Thanks

Harish