Java Stack do not start properly

[steven_bier]

Hi,

i have a problem by starting my Solution Manager Doublestack / SLES10 with MaxDB.

Abap is coming up proper but the Java Stack don´t start.

By restarting the Java stack in Transaction smicm the Java Stack coming up.

But why do the Java Stack don´t startup with the abap stack ?

Following error is shown in Log dev_server0

• TIME Fri Nov 19 10:17:46 2010

* RELEASE 701

* COMPONENT NI (network interface)

* VERSION 38

* RC -5

* MODULE gwxx_mt.c

* LINE 480

* DETAIL timeout 60000 msecs

* SYSTEM CALL NiRead

* COUNTER 1

*

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

JLaunchIExitJava: exit hook is called (rc = -11113)

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

• 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.

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

SigISetIgnoreAction : SIG_IGN for signal 17

JLaunchCloseProgram: good bye (exitcode = -11113)

MaxHeapsize is set.

Computer Hardware is oversized.

License is OK !

It seemed the Abap Stack is starting to slow and the Java Stack can´t connect to the gateway.

Starting time of the Abap Stack is about 12 minutes (extreme long)

thanks

Steven

[steven_bier]

Parameter rdisp/j2ee_start_lazy in Instance Profile solved the Problem.

[Paul_Babier]

Hi

You'd really need to do a trace to find out what is going on, however often it is a user authorization problem.

Sometimes there is a reference to a user that doesn't exist like "Guest" when it should be J2EE_GUEST and this setting needs to be changed from guest to ume.login.guest_user.uniqueids = J2EE_GUEST. But that is just an example of why the java machine might not start automatically, but may when you logon with an authorized user to start it. It may have been an error specifiying a user during setup configurations. So you should make sure the users specified on the Java side also exist in SU01 on the ABAP side. If that's not helpful, you should run a trace to get more information.

Hope this is helpful.

Regards,

Paul

[TomCenens]

Dear Steven

There are multiple thread on the forum about this exitcode, search using terms like J2EE exitcode -11113 or even only using " -11113" and you will bump into the available thread and then you can check all proposed solutions to fix your issue.

Kind regards

Tom

[allam_drebes]

Hello Steven,

You need to check into the logs files dev_dispatcher, std_server0 and dev_bootstrap, they will show you why the J2EE is not starting.

This files are found at the work folder for this instance.

Regards,

Allam