Error: CJS-20057 while Java-Add-In-Installation

[Former Member]

Hi,

I get this error while Java-Add-In-Installation:

ERROR 2005-08-31 09:01:59

CJS-20057 Starting J2EE Engine D01 of SAP system XI3 failed: after 23 seconds the state of the engine changed from "Stopping" to "Stopped".

Who knows the solution?

Thanks.

Greets

Stefan

[Former Member]

Steffan,

I encountered the same error when installing Java in HP-UX OS. In my case this was due to the support packs on ABAP stack. I installed ABAP and applied recent support packs as part of post-install steps and then started the Java Add-in.

I re-installed ABAP Central Instance, Database Finalization and created and performed client copy. Thereafter, started Java Add-In. This time, the Java install completed successfully without the CJS-20057 error.

I hope this approach helps you too!

Regards

Raghu Balasubramanian

[Former Member]

Hello! Steven,

I am getting the same problem? Were you able to fix it? If you did can you give me some guidance on how to go about with VM setting etc to fix the issue?

Regards,

Piyush

[Former Member]

Hi Stefan,

This is one solution that i came across in an alternate thread,

"Not sure if this will help but..

All of my issues resolved around the Java engine (HEAP) not being able to reserve enough memory. Also, I found some of the default parameters in the config tool to be slightly incorrect.

So, I patched to the Java version C:\j2sdk1.4.2_08..I assume you have edited the profile parameter to include

jstartup/vm/home = <your jdsk> location

During the java install, failed at the IGS step (due to IGS running on the Abap stack), had to kill this process with

qprocess sapservice<SID> (look for the IGS processes)

sapntkill -INT pid pid pid (yes, I'm running Windows)

Then, the failure at the Java startup time. Numerous error messages like cj2-20057, or server0 would not start etc. I tried numerous attempts, eventually identifing that the Java parameters were not correct.

So...

Run the configtool.bat

For the instance_ID:-

Message Server and Bootstrap tab

256MB memory

no Java parameters set

Servers General Tab

Max heap size 256MB

-Xms128m

-XX:NewSize=32m

-XX:MaxNewSize=64m

-XX:NewRatio=3

-XX:+DisableExplicitGC

The DISPATCHER ID

General TAB

Ensure the max heap size is 64

-Xms64M

Bootstrap TAB

Max heap size 384

(no JAva parameters set)

the SERVER ID

General TAB

Max Heap Size 528

Java parameters as below....

-Xms528M

-XX:PermSize=192M

-XX:MaxPermSize=192M

-XX:NewSize=160M

-XX:MaxNewSize=160M

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

-verbose:gc

Bootstrap Tab

383MB

-no java parameters set

Shut down the Java stack in MMC, pressed the Retry button, and all was fine.

Hope this helps."

cheers

Sameer

[Former Member]

Hi Sameer,

Thanks for your answer, but the reason of my problem was the virtual memory of my d-particition.

Regards

Stefan