Skip to Content

Jcontrol.exe process getting stopped after installation CI installation

Hi Team,

We have successfully instllaed Enterprise Portal (EP) / SAP Netweaver 7.0, JAVA including EHP1, SR1 on HA MSCS Cluster u2013 2 cluster 4 nodes basis (2Nodes for SAP application and 2Nodes for Database Instance) on Windows 2008 and MS SQL 2008 for Production Environment.

The following components/instances have been installed successfully on Node-A and Node-B.

u2022 Central Services Instances (SCS)

u2022 First MSCS Node

u2022 Database Instance

u2022 Additional MSCS Node

u2022 Enqueue Replication Server

u2022 Central Instance

Now we are facing another issue is that the jcontrol.exe process is getting Stopped of Node-A. We have already updated the latest Kernel files, but still the problem is not resolved of jcontrol.exe.

I am attaching the developer trace error of jcontrol.exe process for your investigation.

-


trc file: "E:\usr\sap\PEP\JC63\work\dev_jcontrol", trc level: 1, release: "701"

-


node name : jcontrol

pid : 4496

system name : PEP

system nr. : 63

started at : Thu Nov 24 20:07:36 2011

arguments :

arg[00] : E:\usr\sap\PEP\JC63\exe\jcontrol.EXE

arg[01] : pf=
VSAPPRDEP1SCS\sapmnt\PEP\SYS\profile\PEP_JC63_ASAPPRDEP1

[Thr 192] Thu Nov 24 20:07:36 2011

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

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

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

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

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

JStartupReadInstanceProperties: read instance properties [E:\usr\sap\PEP\JC63\j2ee\cluster\instance.properties;E:\usr\sap\PEP\JC63\SDM\program\config\sdm_jstartup.properties]

-> ms host : VSAPPRDEP1SCS

-> ms port : 3961

-> OS libs : E:\usr\sap\PEP\JC63\j2ee\os_libs

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Used property files

-> files [00] : E:\usr\sap\PEP\JC63\j2ee\cluster\instance.properties

-> files [01] : E:\usr\sap\PEP\JC63\SDM\program\config\sdm_jstartup.properties

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

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

Instance properties

-> ms host : VSAPPRDEP1SCS

-> ms port : 3961

-> os libs : E:\usr\sap\PEP\JC63\j2ee\os_libs

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Bootstrap nodes

-> [00] bootstrap : E:\usr\sap\PEP\JC63\j2ee\cluster\instance.properties

-> [01] bootstrap_ID63102180 : E:\usr\sap\PEP\JC63\j2ee\cluster\instance.properties

-> [02] bootstrap_ID63102185 : E:\usr\sap\PEP\JC63\j2ee\cluster\instance.properties

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

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

Worker nodes

-> [00] ID631021800 : E:\usr\sap\PEP\JC63\j2ee\cluster\instance.properties

-> [01] ID631021850 : E:\usr\sap\PEP\JC63\j2ee\cluster\instance.properties

-> [02] sdm : E:\usr\sap\PEP\JC63\SDM\program\config\sdm_jstartup.properties

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

[Thr 192] JControlExecuteBootstrap: execute bootstrap process [bootstrap]

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

Java Home: C:\j2sdk1.4.2_17-x64

[Thr 192] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\PEP\JC63\exe\jvmx.jar

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

JStartupIReadSection: read node properties [bootstrap]

-> node name : bootstrap

-> node type : bootstrap

-> node execute : yes

-> java path : C:\j2sdk1.4.2_17-x64

-> java parameters : -Djco.jarm=1

-> java vm version : 1.4.2_17-b06

-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)

-> java vm type : server

-> java vm cpu : amd64

-> heap size : 256M

-> root path : E:\usr\sap\PEP\JC63\j2ee\cluster

-> class path : .\bootstrap\launcher.jar

-> OS libs path : E:\usr\sap\PEP\JC63\j2ee\os_libs

-> main class : com.sap.engine.offline.OfflineToolStart

-> framework class : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path : E:\usr\sap\PEP\JC63\exe\jstartup.jar;E:\usr\sap\PEP\JC63\exe\jvmx.jar

-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID6310218

-> debuggable : yes

-> debug mode : no

-> debug port : 60000

-> shutdown timeout : 120000

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

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

JControlStartJLaunch: program = E:\usr\sap\PEP\JC63\exe\jlaunch.exe

-> arg[00] = E:\usr\sap\PEP\JC63\exe\jlaunch.exe

-> arg[01] = pf=
VSAPPRDEP1SCS\sapmnt\PEP\SYS\profile\PEP_JC63_ASAPPRDEP1

-> arg[02] = -DSAPINFO=PEP_63_bootstrap

-> arg[03] = -nodeId=-1

-> arg[04] = -file=E:\usr\sap\PEP\JC63\j2ee\cluster\instance.properties

-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_4496

-> arg[06] = -nodeName=bootstrap

-> arg[07] = -jvmOutFile=E:\usr\sap\PEP\JC63\work\jvm_bootstrap.out

-> arg[08] = -stdOutFile=E:\usr\sap\PEP\JC63\work\std_bootstrap.out

-> arg[09] = -locOutFile=E:\usr\sap\PEP\JC63\work\dev_bootstrap

-> arg[10] = -mode=BOOTSTRAP

-> arg[11] = pf=
VSAPPRDEP1SCS\sapmnt\PEP\SYS\profile\PEP_JC63_ASAPPRDEP1

-> lib path = PATH=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\PROGRA2\CA\SC\CCS\ETPKI\lib;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\CA\CA_APPSW;C:\PROGRA2\CA\SC\CCS\CAM\bin;C:\PROGRA2\CA\SC\CCS\PDA;C:\Program Files (x86)\CA\SC\CCS\AT\services\bin;C:\Program Files (x86)\CA\SC\CCS\AT\agents\bin;C:\PROGRA2\CA\NSM\bin;C:\PROGRA~2\CA\SC\CCS\AT\Agents\bin;F:\usr\sap\PEP\SYS\exe\uc\NTAMD64

-> exe path = PATH=C:\j2sdk1.4.2_17-x64\bin;E:\usr\sap\PEP\JC63\j2ee\os_libs;C:\PROGRA2\CA\SC\CCS\ETPKI\lib;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\CA\CA_APPSW;C:\PROGRA2\CA\SC\CCS\CAM\bin;C:\PROGRA2\CA\SC\CCS\PDA;C:\Program Files (x86)\CA\SC\CCS\AT\services\bin;C:\Program Files (x86)\CA\SC\CCS\AT\agents\bin;C:\PROGRA2\CA\NSM\bin;C:\PROGRA~2\CA\SC\CCS\AT\Agents\bin;F:\usr\sap\PEP\SYS\exe\uc\NTAMD64

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

[Thr 192] Thu Nov 24 20:07:38 2011

[Thr 192] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c 1642]

[Thr 192] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)

[Thr 192] JControlCloseProgram: started (exitcode = 66)

[Thr 192] JControlCloseProgram: good bye... (exitcode = 66)

-


I would appreciate, if any one can reply and provide the solution for this process ASAP.

Thanking you,

Devki Nandan

Edited by: D.N. Bhatt on Nov 27, 2011 3:02 PM

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

5 Answers

  • Nov 27, 2011 at 10:39 AM

    Hi,

    1. Shut down the server instance completely

    2. In Windows Run Menu Type Services.msc.

    3. Locate the servuce MaxDB: <Instance Name>

    4. Start the service

    5. To avoid this issue in future change the startup type from manual to automatic.

    6. Start the Server now.

    Thanks

    Prashant

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Prashant,

      Thanks for your reply..!!

      I did not find the service MaxDB: <Instance Name> in the service.msc may be because we have the SQL DB 2008 on Windows2008.

      Is there any thing I have to do.?

      Thanks!

      Devki N Bhatt

  • Nov 29, 2011 at 04:34 PM

    Dear Mr. Bhatt,

    Hope you are doing good.

    This seems to be aissue with the bootstrap process:

    "

    ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c 1642] [Thr 192] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66) [Thr 192] JControlCloseProgram: started (exitcode

    "

    After a restart, do chec the below files, and you should be able to find the root cause:

    /usr/sap/<SID>/work/ dev, std and jvm*

    and

    /usr/sap/<SID>/DV<nr>/j2ee/cluster/bootstrap/system.log

    Thank you and have a nice day :).

    _____________

    Kind Regards,

    Hemanth

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 04, 2011 at 07:15 PM

    Dear Hemanth,

    Thanks for your valuable reply.

    I have gone the all possible error logs and found in the error u201CID631021800" does not exist. I have replaced the instance.properties on Node-B from Node-A after taking backup of the existing property file at directory E:\usr\sap\SID\JC63\j2ee\cluster, as the ID were different. And after replacing this file, I have observed that now the jcontrol.exe process is not dying now but getting standstill (hanged) because of the AS Java Process Table (dispatcher & server0) stopped of Node-B but SDM is running.

    Also checked the profiles SID_JC63_hostname-A and SID_JC63_hostname-B under
    <virtual_host\sapmnt\<SID>\SYS\profile and found the j2ee/instance_ids are different for both nodes which I tried to replace with each other and also tried to keep same type of ID at both profiles but no success.

    When I checked the developer trace of dying process (dev_dispatcher) found the below error :

    ===============================================================================================

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

    JHVM_BuildArgumentList: main method arguments of node [dispatcher]

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

    [Thr 3456] Sun Dec 04 16:44:50 2011

    [Thr 3456] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

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

    [Thr 3456] JLaunchISetClusterId: set cluster id 631021800

    [Thr 5848] JLaunchIExitJava: exit hook is called (rc = -337)

    *[Thr 5848] ***********************************************************************

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

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

    [Thr 5848] JLaunchCloseProgram: good bye (exitcode = -337)

    ===============================================================================================

    In the developer trace, it suggests the SAP Note 943602 for J2EE Engine exit code and this note refer another note u2013 940893 which requires a more detailed analysis.

    Kindly let me know and suggest for any changes/notes which requires for this resolution ASAP.

    Thanks!

    Devki N Bhatt

    Edited by: D.N. Bhatt on Dec 5, 2011 2:09 AM

    Edited by: D.N. Bhatt on Dec 5, 2011 2:13 AM

    Edited by: D.N. Bhatt on Dec 5, 2011 2:15 AM

    Edited by: D.N. Bhatt on Dec 5, 2011 2:18 AM

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 05, 2011 at 06:23 AM

    Hi,

    I also checked Database connectivity on the both Nodes (Cluster Node A & B) and got the below error:

    ----


    E:\usr\sap\PEP\JC63\exe>R3trans -d

    This is R3trans version 6.14 (release 701 - 03.06.11 - 17:57:00).

    unicode enabled version

    2EETW169 no connect possible: "connect failed with DBLI_RC_LOAD_LIB_FAILED."

    R3trans finished (0012).

    ----


    If need further information, please do let me know. Awaiting reply for quick resolution on this error.

    Thanks!

    Devki Nandan

    Edited by: D.N. Bhatt on Dec 5, 2011 11:54 AM

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 05, 2011 at 11:36 AM

    Dear Mr. Bhatt,

    Hope you are doing good.

    If the server reaches a state where the dispatcher node is trying to startup, then the issue hould not be just DB connecion error. If so, it would have stopped with the bootstrap process.

    First of all I would request you to login to the config tool ->instance and check the dispatcher ID there (is it ID631021800?). Also

    navigate to managers-> cluster manager and check the value of element.clusterID for the dispatcher. Also check the same for server nodes as well.

    Most probably, these values will be different. Also make sure that the same are set in the global and the local level as well.After making the changes, please do a cluster restart for the changes to take effect.

    Steps:

    1. Launch configtool and switch to configuration editor mode (pencilicon)

    2. Navigate to cluster_data -> dispatcher and check for the entry ID631021800.

    3. If it's not there then it's an installation issue.

    4.If it is there please check the ID is same as the ID in the instance.properties which is located in $(DIR_INSTANCE)/j2ee/cluster

    5. If you just do a system copy,please reference to note: 966752 to help you solve the problem.

    Kindly check the SAP note: 812910 which deals with the same issue. In most cases we have seen this issue when the system copy was not done via the sapinst tool. Please can you confirm the system copying strategy used?

    Thank you and have a nice day!

    _____________

    Kind Regards,

    Hemanth

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Devki Nandan Bhatt

      Hi,

      It seems that both of your Instances have the same ID, and the ID's should be unique and different.

      This mean that your instances were not properly installed.

      Therefore it is best to delete the second instance, and re-installed it.

      Refer to note

      Note 871523 - Removing dialog instance from database after uninstallation

      Regards,

      Ventsi Tsachev