The connectivity between ABAP and JAVA system is not working properly.

[Former Member]

Hi,

I have Installed ECC5.0 ABAP system and Netweaver JAVA system with different SID's in single box. While Installing JAVA systen I have selected UME as ABAP system and Installation was success. Once I restart MMC the JAVA server process thowing an rc -11113.

I have pasted trace file for Server process. Please send me any suggestions ASAP.

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

[Thr 4500] JLaunchISetClusterId: set cluster id 31689350

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

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

[Thr 4180] Thu Apr 19 12:06:29 2007

[Thr 4180] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver

[Thr 4180] JHVM_RegisterNatives: registering methods in com.sap.mw.jco.util.SAPConverters

[Thr 4180] JHVM_RegisterNatives: registering methods in com.sap.mw.jco.util.SAPCharToNUCByteConverter

[Thr 4180] JHVM_RegisterNatives: registering methods in com.sap.mw.jco.util.SAPNUCByteToCharConverter

[Thr 4748] Thu Apr 19 12:06:30 2007

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

[Thr 4748] **********************************************************************

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

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

• for additional information and trouble shooting.

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

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

Thanks,

Suraj

[Former Member]

Hi Suraj,

Please check this thread:

Please award points if solved.

Regards.

Ruchit.

[Former Member]

Hi,

I have gone through notes and I changed Parameters what they specified in note. But still problem exists.

Thanks,

Suraj

[Former Member]

follow Note 943498 - J2EE Engine does not start 6.40 and 7.0

Cheers,

-Sunil

[Former Member]

Hi,

It clearly says the problem is with virtual memory. SO you need to change your virtual memory settings using configtool.

See the relevant note.940893

Make changes in the VM parameters for Bootstarp, Dispatched and the server nodes. Your -Xms should be less than equal to -Xmx.

Restart the cluster then.

It should work.

Do reward good points.