JAVA Engine not starting on Solaris 10 / Oracle 10 / AMD64

[Former Member]

Hi there, I have been battling installing SSM 4.0 SR2 on a AMD64 Opteron Server, running Solaris 10 and Oracle 10. I had to download the 32bit Sun JDK 1.4.2_14 as well as the obscure 64-bit JDK for AMD64 (from Sun's site). My installation bombs out when it tries to start up the Java engine the first time, with this error in the dev_bootstrap file:

Error occurred during initialization of VM

Signal chaining not allowed for VM interrupt signal, try -XX:+UseAltSigs.

[Thr 4] JLaunchIAbortJava: abort hook is called

[Thr 4] **********************************************************************

• ERROR => The Java VM aborted unexpectedly.

• Please see SAP Note 943602 , section 'Java VM crashes'

• for additional information and trouble shooting.

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

[Thr 4] SigISetIgnoreAction : SIG_IGN for signal 18

[Thr 4] JLaunchCloseProgram: good bye (exitcode = -2)

Anyone had this particular problem?

[raguraman_c]

Hi,

Check this,

http://www.velocityreviews.com/forums/t141333-problem-loading-jni-library.html

This will solve your problem.

Feel free to revert back.

--Ragu

[Former Member]

Sorry, I do not understand the answer.

We have a similar problem in installing an distributed CI of a NW2004s system on Solaris/x64.

In the definition of the java users wioth get an error in the file UserCheck.log.

>>>

Error occurred during initialization of VM

Signal chaining not allowed for VM interrupt signal, try -XX:+UseAltSigs.

>>>

What is the solution?

[Former Member]

Hi Thomas, I got past the CreateJSF, CreateJ2EEAdmin and CreateJ2EEGuest steps by manually creating these users in the ABAP client 001. Create SAPJSF as Comms user with role SAP_BC_JSF_COMMUNICATION_RO, create J2EE_ADMIN Dialog user with role SAP_J2EE_ADMIN and create J2EE_GUEST Dialog user with role SAP_J2EE_GUEST. When u run SAPINST, it will give an error when trying to create SAPJSF -> stop the installation, edit the keydb.xml (under the temporary installation folder) and search for ERROR, then replace ERROR with OK. Start SAPINST again and continue the previous installation. Every time it gives an error with creating the user, just stop, edit the keydb.xml file and restart SAPINST.

I got past the user creations, but I have an issue now with the step where it tries to start the JAVA engine. Will keep you posted.

[Former Member]

Thank you for the answer.

A colleague opened a problem in the service market place.

Let's see if we will get a solution for this.

I will keep you informed.

Regards,

Thomas.

[Former Member]

Hi Thomas, I have also opened an OSS message. Here is the response:

Have you created the user SAPJSF and J2EE_ADMIN manually and grant the

right authorization for them?

SAPJSF needs role SAP_BC_JSF_COMMUNICATION in tx SU01.

See the link:

http://help.sap.com/saphelp_nw04/helpdata/en/8f/

67d27676ace84080964d4c4223bb3c/frameset.htm

If so I would suggest you to skip the error by running the command:

1 ./sapinst SAPINST_SKIP_ERRORSTEP=true

Else you can edit the keydb.xml file

2.- change 'keydb.xml' => change to OK the status of step J2EE_ADMIN

</strval>

</fld>

<fld name="STATUS">

<strval><![CDATA[ERROR]]> (chane the ERROR code to OK)

</strval>

</fld>

Also:

- check if the users are not locked!

- try restarting JAVA:

1. stop J2EE engine by user sm2adm: stopsap j2ee

2. start J2EE engine by user sm2adm: startsap j2ee

3. wait until the J2EE is fully started, check the JLaunchISetState. 4. run ./sapinst SAPINST_SKIP_ERRORSTEP=true

If all the above are correct, then the problem is that the SAPJSF

password is incorrectly set in the UME properties. Please see the

following URL for details on how to change this:

http://help.sap.com/saphelp_nw04/helpdata/en/84/

10594aecd3e1408845e66c432b955e/content.htm

If this won't help send the message back to me with attached the dev_ms,dev_enqio_0, sapinst1 and the last sapinst_dev files for analysis.

[Former Member]

We got an answer from SAP.

The used jdk (version 1.4.2_14) is currently under examination by SUN.

We should use the version 1.4.2_11.

Now I wonder were to find this version. The 32bit package is in the archives of sun.

Currently I do not know were to get the 64bit package.

Thomas.

[Former Member]

Yes, u r absolutely correct. I have also seen forums etc mentioning JDK1.4.2_11 that works, but the only available SUN JDK for AMD64 is version 1.4.2_14. I have no idea where to get the 11 version. See OSS note 941595 regarding this issue. The SUN link for SAP customers is http://java.sun.com/j2se/1.4.2/SAPsite/download.html but u need online account (free). Maybe SAP should release version 11 on their website.

[Former Member]

I found it.

You just have to spoof the link.

Just try that:

<a href="http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=22&PartDetailId=j2sdk-1.4.2_11-amd64-JPR&SiteId=JSC&TransactionId=try">j2sdk-1.4.2_11</a>

It works.

[Former Member]

Fantabulous! Busy downloading it. Got the 32-bit Version 11 same way, so finally I can kick some SolMan butt!!!

Thanks for the link!

[Former Member]

By the way.

The "normal" jdk's (32bit) you can get from the following official link:

http://java.sun.com/products/archive/j2se/1.4.2_11/index.html<a href="http://java.sun.com/products/archive/j2se/1.4.2_11/index.html">j2se archive</a>

Now our installation have no problems to create the java users.

Thomas.