7/31/2019 Note 943498 - J2EE Engine Does Not Start 6.40 and 7.0

http://slidepdf.com/reader/full/note-943498-j2ee-engine-does-not-start-640-and-70 1/2

26.10.2008 Page 1 of 2

Note 943498 - J2EE Engine does not start 6.40 and 7.0

Note Language: English Version: 5 Validity: Valid from 30.05.2006

Summary

SymptomThe J2EE Engine 6.40 or 7.0 does not start or a runtime error stopped it

More Termsj2ee, startup framework, jcontrol, jlaunch, jstart, problem report, Engine

not starting

Cause and PrerequisitesIn order to speed up processing the problem with SAP support this note

helps to collect the most relevant information to track down the problem.

Additional information can be found in note 940893.

Confirmation of the VM in use

Please check if the correct Version of the JDK is applied with help of the

appropriate note:

716604 for the Sun JDK (Windows, Linux, Solaris)

716926 for the HP JDK (HP-UX)

722520 for the Tru64 JDK *

716927 for the IBM JDK (AIX)717376 for the IBM JDK (iSeries, OS/400)

746299 for the IBM JDK (zSeries)

746203 for the IBM JDK (zOS)

810008 for the IBM JDK (Linux on POWER)

861215 for the IBM JDK (AMD64/EM64T-Linux)

718901 How to Change the JDK of the J2EE Engine

* supported on 6.40 only, not on 7.00

To identify the current version of the JDK, please execute

java -version

on command line.

In addition check if there are redundant versions and make sure that the

right version of the JDK is used by the SAP J2EE Engine.

Check if JAVA_HOME environment variable is set and verify the value of

jstartup/vm/home parameter in the instance profile.

It is also important to verify the user rights on Unix systems.

SolutionPlease follow the steps described below to get some initial hints on the

problem:

1. Open the dev_jcontrol developer trace file in the

\\usr\sap\J2E\<InstNo>\work directory and see if the text contains an

7/31/2019 Note 943498 - J2EE Engine Does Not Start 6.40 and 7.0

http://slidepdf.com/reader/full/note-943498-j2ee-engine-does-not-start-640-and-70 2/2