J2EE ENGINE don't start when sapinst is running

[Former Member]

hi.

I try to install java add-in on existing abap system. installing of central instance is running and when start java engine execute i recive error:

Java processes of instance CEM/DVEBMGS15 [ABAP: ACTIVE, Java: UNKNOWN] did not reach state PARTRUNNING after 20:00 minutes. Giving up.

what's a problem?

[Former Member]

i am shure you get another error explained in note 1048824.

you must add "jstartup/signal_handling=0" in <b>default</b> file ( i use solaris and maxdb ) or in instance startup parameters file ( other SO ).

this solve my problem during install of solution manager 4.0

Message was edited by:

Mugur Enache

[Ranjeet0702]

you need to stop the instance before starting the Java stack installation.

[Former Member]

instance not running before instalation(stoped by sap managment console ), sapinst start instance during installation.

[suresh_krishnamoorthy]

Hi Denis,

Check your heap size. see this thread:

Regards, Suresh KB

[Former Member]

heap size is critical for 32-bit platform, but i have 64-bit windows, am i right?

in log dev_jcontrol i see:

"[Thr 4224] [Node: server0] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_09

[Thr 4224] JStartupICheckFrameworkPackage: can't find framework package C:\usr\sap\CEM\DVEBMGS15\exe\jvmx.jar

"

is that cause?

[Former Member]

Check to see it that file (jvmx.jar) is installed in that directory first.

[Former Member]

Hi All,

i am also getting the same problem.

In my case, jvmx.jar is not created.

Please let me know, what should i do?

Regards

Piyush

[Former Member]

Hi, Denis.

I have same problem. jvmx.jar is not created.

What action made you to resolve this bug ?

Thx

Alexei Rylov

PS.: My thread is: [threadID=833130|;

[Former Member]

Check if you have any firewall or other software running. I got this problem of server not starting when BLACKICE was running. When I killed the process and retried, it worked.

Cheers,

Sandeep

[martin_juen2]

hi.

first of all start jcmon and have a look what's not starting. then check the log files - the most interesting info is located there.

regards,

martin