cancel
Showing results for 
Search instead for 
Did you mean: 

The Java VM terminated with a non-zero exit code

Former Member
0 Kudos

Hi SDN,

'The Java VM terminated with a non-zero exit code.'

I have got this error when I am trying to restart my AS JAVA sneak preview. Everything was working fine until this restart. The J2EE engine is not starting up again.

Can someone suggest me how can I fix this.

Thanks,

Vamshi

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Vamsi,

Its because u have changed the data source on UME. If u have installed JAVA instance alone the database used for saving all the user master records will be the same JAVA database. However if u have both ABAP and JAVA engine the user master data will be stored in ABAP datasource. If u have tried to change them the system will not start up for the next time.

To bring back the settings we can use config tool and in the service com.core.security.ume ( sorry something like this will be there which i dont remember exactly ) make the values to a default one OR if u are sure with the values you can be specific. After that you server should start.

regards,

Anandh

Answers (8)

Answers (8)

former_member250109
Discoverer
0 Kudos

A little late but this what I found:

Check the user that is in the J2EE Config Tool used for connecting to the UME on the ABAP instance.

You can find it in Cluster-data -> Instance_IDxxxxxxxx -> Server_IDyyyyyyyy -> Services ->

com.sap.security.core.ume.service

Key: "ume.r3.connection.master.user"  the value is usually "SAPJSF".

Check if this user is not locked in the ABAP instance and the password in key "ume.r3.connection.master.passwd" is correct.

I unlocked the user and started Server0 in the AS Java Process Table and ... Succes!

Cheers!

James_Connolly
Employee
Employee
0 Kudos

(rc = -11113) is a failed service start.

In these cases the std_server0 log is where you look to find which service has failed.

It's the UME as you have found.

std_bootstrap really only ever contains a header.

jvm_server.out never contains any info.

Former Member
0 Kudos

Hello,

In my case, Dispatcher was yellow and disp log giving same message. ABAP instance up but JAVA was down. ** I simply restart  Dispatcher. ++. Now JAVA also available..

Cheers,

Rahul

Former Member
0 Kudos

Hi,

Check the validity of your license.

Cheers,

Ridouan

Former Member
0 Kudos

hi,

i think this the problem of user roles.plz check all java user and roles.those are in yellow compare all roles.then start the server.

regards

ajai

Former Member
0 Kudos

Hi,

I have changed the settings to default and it is working fine.

Thank you All.

Vamshi

Former Member
0 Kudos

Hi Vamsi,

Can you give the what are setting you did.

Regards,

Kannan

Former Member
0 Kudos

Hi,

This might be caused by the safe mode set as default. Check<a href="http://help.sap.com/saphelp_nw04/helpdata/en/43/1c3e6811a52d23e10000000a1553f7/frameset.htm">this</a> page and see if manually switching safe mode off will solve the problem. If this solution not solved your problem, put the std_server0.out file

Former Member
0 Kudos

Hi,

This is the problem with VM settings.

Some specific settings have to be done.

Go through the note 940893 and 129813.

Also paste the logs for further analysis.

Reward points if useful

Regads,

Nayana

Former Member
0 Kudos

HI Nayana, Vijith.

I am pasting the log file here.

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

JHVM_BuildArgumentList: main method arguments of node [server0]

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

[Thr 1564] Sat Jul 28 06:23:37 2007

[Thr 1564] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

[Thr 1564] Sat Jul 28 06:23:38 2007

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

[Thr 1564] JLaunchISetClusterId: set cluster id 19476550

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

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

[Thr 3360] Sat Jul 28 06:24:17 2007

[Thr 3360] JLaunchIExitJava: exit hook is called (rc = -11113)

[Thr 3360] **********************************************************************

      • ERROR => The Java VM terminated with a non-zero exit code.

      • Please see SAP Note 943602 , section 'J2EE Engine exit codes'

      • for additional information and trouble shooting.

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

[Thr 3360] JLaunchCloseProgram: good bye (exitcode = -11113)

Thanks,

Vamshi

Former Member
0 Kudos

Hi,

Can you check your file system.

Also have changed your UME Source?

Thanks & Regards,

Vijith

Former Member
0 Kudos

Hi,

Look carefuly for errors in the other log files in the work directory of the JC00 folder:

std_bootstarp.

jvm_server.out

..

Let me know what you found.

Former Member
0 Kudos

Hi,

Look carefuly for errors in the other log files in the work directory of the JC00 folder:

std_bootstarp.

jvm_server.out

..

Let me know what you found.

Former Member
0 Kudos

Hi,

Go to configtool and change the heap size.

present in C:\usr\sap\SID\JCxxj2ee\configtool.

Can you mention whether it is a 32 bit or 64 bit machine.

There are diffrent settings to be done for both the machines.

Also mention what is the current heap size, so that i can suggest some settings to make the instance come up.

Reward points if useful.

regards,

nayana

Former Member
0 Kudos

Hi,

Please do put the dev_jcontrol and bootstrap file to analyze.

Thanks & Regards,

Vijith