cancel
Showing results for 
Search instead for 
Did you mean: 

JControl fails at start

Former Member
0 Kudos

We just added a dialog instance on a new server, sapinst runs all the way through, but fails because it cannot start the instance.

This is the trace file for dev_Jcontrol.

I do remember this is kind of a false error, because all of the java settings are correct. Can anybody help us with this?

-


trc file: "D:\usr\sap\PP1\J00\work\dev_jcontrol", trc level: 1, release: "700"

-


node name : jcontrol

pid : 3544

system name : PP1

system nr. : 00

started at : Wed May 16 15:05:37 2007

arguments :

arg[00] : D:\usr\sap\PP1\J00\exe\jcontrol.EXE

arg[01] : pf=
bksaprtlc1\sapmnt\PP1\SYS\profile\PP1_J00_bksaprtld1

[Thr 2100] Wed May 16 15:05:37 2007

[Thr 2100] *** WARNING => INFO: Unknown property [instance.en.host=bksaprtlc1] [jstartxx.c 841]

[Thr 2100] *** WARNING => INFO: Unknown property [instance.box.number=PP1J00bksaprtld1] [jstartxx.c 841]

[Thr 2100] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c 841]

[Thr 2100] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]

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

JStartupReadInstanceProperties: read instance properties [D:\usr\sap\PP1\J00\j2ee\cluster\instance.properties]

-> ms host : bksaprtlc1

-> ms port : 3900

-> OS libs : D:\usr\sap\PP1\J00\j2ee\os_libs

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Used property files

-> files [00] : D:\usr\sap\PP1\J00\j2ee\cluster\instance.properties

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

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

Instance properties

-> ms host : bksaprtlc1

-> ms port : 3900

-> os libs : D:\usr\sap\PP1\J00\j2ee\os_libs

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Bootstrap nodes

-> [00] bootstrap : D:\usr\sap\PP1\J00\j2ee\cluster\instance.properties

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

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

Worker nodes

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

[Thr 2100] [Node: bootstrap] java home is set by profile parameter

Java Home: d:\usr\java

[Thr 2100] *** ERROR => JStartupIGetJDKInfo: Cannot find Java compiler [d:\usr\java\bin\javac.exe]. [jstartxxi.c 968]

[Thr 2100] *** ERROR => can't get JDK information (rc = -1) [jstartxxi.c 1240]

[Thr 2100] **********************************************************************

      • ERROR => JDK Detection failed.

      • Please see SAP Note 943602 , section 'JDK detection issues'

      • for additional information and trouble shooting.

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

[Thr 2100] *** ERROR => can't read bootstrap node properites (rc=-1) [jcntrxx.c 1247]

[Thr 2100] JControlCloseProgram: started (exitcode = -1)

[Thr 2100] JControlCloseProgram: good bye... (exitcode = -1)

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Perry,

Is your JAVA_HOME environment variable set correctly in all locations? You should add the jre path (d:\usr\java\bin) to the system path variable.

<i>Cannot find Java compiler [d:\usr\java\bin\javac.exe].</i>

-jwise

Former Member
0 Kudos

Yes, the following has been set:

SAPINST_JRE_HOME = D:\usr\java

JAVA_HOME = D:\usr\java

Appended to PATH: D:\usr\java\bin

Former Member
0 Kudos

> Yes, the following has been set:

> JAVA_HOME = D:\usr\java

> Appended to PATH: D:\usr\java\bin

Ah, but HOW did you set them

Make sure they are System variables (the lower frame of Environment Variables screen), and not User variables (the top frame).

Been there, done that, got the t-shirt.

Answers (3)

Answers (3)

Former Member
0 Kudos

Well, believe it or not, it had nothing to do with java path, it was a permissions issue. I went back to the install docs. it said that SAPService<SID> should not be a member of domain users and its primary group should be SAP_<SID>_GlobalAdmin. I made the changes, and "VIOLA", it started....

Former Member
0 Kudos

Hi Perry,

See if this helps :

The engine is not able to start due to problems detecting the JDK.

<b>1.</b> Check that you have installed the correct JDK version. Read the section entitled 'Confirmation of the VM in use' in Note 943498 to find the appropriate platform-specific note.

To identify the current version of the JDK, execute the following command at command line level:

java -version You must have installedthe complete JDK/JSDK (including the Java Compiler javac).

<b>2.</b> Check if there are redundant JDK versions and make sure that the SAP J2EE Engine uses the correct JDK version. Therefore, <b>verify thecorresponding parameter in the instance profile

/usr/sap/<SID>/SYS/profile/<SID>_JC<num>_<host>

jstartup/vm/home = <jdk home directory>.

This parameter has a higher priority than the environment variable JAVA_HOME. </b> - On Unixsystems, it is important to verify the user rights.

If you experience problems with the JDK, open a message under the component for the relevant JDK provider (for example, BC-OP-SUN-JSE).

Thanks,

Sai Kondapi.

Former Member
0 Kudos

Hi Perry ,

Apart from what has been mentioned refer to these threads they also had same problems

<b>>

thanx

Pankaj