cancel
Showing results for 
Search instead for 
Did you mean: 

Java engine is not coming up

Former Member
0 Kudos

Hi,

My java engine is not coming up for some strange reason. Here is a partial log of dev_server0:

-


trc file: "/usr/sap/GSQ/DVEBMGS02/work/dev_server0", trc level: 1, release: "700"

-


node name : ID26770150

pid : 1314818

system name : GSQ

system nr. : 02

started at : Sun Sep 13 05:02:27 2009

arguments :

arg[00] : /usr/sap/GSQ/DVEBMGS02/exe/jlaunch

arg[01] : pf=/usr/sap/GSQ/SYS/profile/GSQ_DVEBMGS02_GILSAPEQ

arg[02] : -DSAPINFO=GSQ_02_server

arg[03] : pf=/usr/sap/GSQ/SYS/profile/GSQ_DVEBMGS02_GILSAPEQ

arg[04] : -DSAPSTART=1

arg[05] : -DCONNECT_PORT=64998

arg[06] : -DSAPSYSTEM=02

arg[07] : -DSAPSYSTEMNAME=GSQ

arg[08] : -DSAPMYNAME=GILSAPEQ_GSQ_02

arg[09] : -DSAPPROFILE=/usr/sap/GSQ/SYS/profile/GSQ_DVEBMGS02_GILSAPEQ

arg[10] : -DFRFC_FALLBACK=ON

arg[11] : -DFRFC_FALLBACK_HOST=localhost

[Thr 1] Sun Sep 13 05:02:27 2009

[Thr 1] *** WARNING => INFO: Unknown property [instance.box.number=GSQDVEBMGS02gilsapeq] [jstartxx_mt. 841]

[Thr 1] *** WARNING => INFO: Unknown property [instance.en.host=GILSAPEQ] [jstartxx_mt. 841]

[Thr 1] *** WARNING => INFO: Unknown property [instance.en.port=3203] [jstartxx_mt. 841]

[Thr 1] *** WARNING => INFO: Unknown property [instance.system.id=2] [jstartxx_mt. 841]

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

JStartupReadInstanceProperties: read instance properties [/usr/sap/GSQ/DVEBMGS02/j2ee/cluster/instance.properties]

-> ms host : GILSAPEQ

-> ms port : 3903

-> OS libs : /usr/sap/GSQ/DVEBMGS02/j2ee/os_libs

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Used property files

-> files [00] : /usr/sap/GSQ/DVEBMGS02/j2ee/cluster/instance.properties

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

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

Instance properties

-> ms host : GILSAPEQ

-> ms port : 3903

-> os libs : /usr/sap/GSQ/DVEBMGS02/j2ee/os_libs

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Bootstrap nodes

-> [00] bootstrap : /usr/sap/GSQ/DVEBMGS02/j2ee/cluster/instance.properties

-> [01] bootstrap_ID26770100 : /usr/sap/GSQ/DVEBMGS02/j2ee/cluster/instance.properties

-> [02] bootstrap_ID26770150 : /usr/sap/GSQ/DVEBMGS02/j2ee/cluster/instance.properties

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

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

Worker nodes

-> [00] ID26770100 : /usr/sap/GSQ/DVEBMGS02/j2ee/cluster/instance.properties

-> [01] ID26770150 : /usr/sap/GSQ/DVEBMGS02/j2ee/cluster/instance.properties

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

[Thr 1] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 1] JLaunchRequestQueueInit: create pipe listener thread

[Thr 258] JLaunchRequestFunc: Thread 258 started as listener thread for np messages.

[Thr 515] WaitSyncSemThread: Thread 515 started as semaphore monitor thread.

[Thr 1] SigISetDefaultAction : default handling for signal 20

[Thr 1] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 1] CPIC (version=700.2009.02.11)

[Thr 1] [Node: server0] java home is set by profile parameter

Java Home: /usr/java14_64

[Thr 1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/GSQ/DVEBMGS02/exe/jvmx.jar

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

JStartupIReadSection: read node properties [ID26770150]

-> node name : server0

-> node type : server

-> node execute : yes

-> jlaunch parameters :

-> java path : /usr/java14_64

-> java parameters : -Xj9 -Xmn400m -Xgcpolicy:gencon -verbose:gc -Djco.jarm=1 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer

-> java vm version : J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142-20080510 (JIT enabled)

-> java vm vendor : IBM J9 VM (IBM Corporation)

-> java vm type : server

-> java vm cpu : ppc64

-> heap size : 2048M

-> init heap size : 2048M

-> root path : /usr/sap/GSQ/DVEBMGS02/j2ee/cluster/server0

-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.

-> OS libs path : /usr/sap/GSQ/DVEBMGS02/j2ee/os_libs

-> main class : com.sap.engine.boot.Start

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

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

-> framework path : /usr/sap/GSQ/DVEBMGS02/exe/jstartup.jar:/usr/sap/GSQ/DVEBMGS02/exe/jvmx.jar

-> shutdown class : com.sap.engine.boot.Start

-> parameters :

-> debuggable : no

-> debug mode : no

-> debug port : 50221

-> shutdown timeout : 120000

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

[Thr 1] JLaunchISetDebugMode: set debug mode [no]

[Thr 772] JLaunchIStartFunc: Thread 772 started as Java VM thread.

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

JHVM_LoadJavaVM: VM Arguments of node [server0]

-> stack : 1048576 Bytes

-> arg[ 0]: exit

-> arg[ 1]: abort

-> arg[ 2]: vfprintf

-> arg[ 3]: -Xj9

-> arg[ 4]: -Xmn400m

-> arg[ 5]: -Xgcpolicy:gencon

-> arg[ 6]: -verbose:gc

-> arg[ 7]: -Djco.jarm=1

-> arg[ 8]: -Djava.security.policy=./java.policy

-> arg[ 9]: -Djava.security.egd=file:/dev/urandom

-> arg[ 10]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-> arg[ 11]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-> arg[ 12]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-> arg[ 13]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer

-> arg[ 14]: -Dsys.global.dir=/usr/sap/GSQ/SYS/global

-> arg[ 15]: -Dapplication.home=/usr/sap/GSQ/DVEBMGS02/exe

-> arg[ 16]: -Djava.class.path=/usr/sap/GSQ/DVEBMGS02/exe/jstartup.jar:/usr/sap/GSQ/DVEBMGS02/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.

-> arg[ 17]: -Djava.library.path=/usr/java14_64/jre/bin:/usr/java14_64/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/GSQ/DVEBMGS02/exe:/usr/sap/GSQ/DVEBMGS02/exe:/usr/sap/GSQ/DVEBMGS02/exe:/tmp/sapinst_exe.856178.1252452114:/usr/sap/GSQ/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/java14_64/jre/bin/j9vm:/usr/sap/GSQ/DVEBMGS02/exe::/usr/lib:/usr/sap/GSQ/DVEBMGS02/j2ee/os_libs:/usr/sap/GSQ/DVEBMGS02/exe:/usr/sap/GSQ/DVEBMGS02/exe:/usr/sap/GSQ/DVEBMGS02/exe:/usr/java14_64/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/GSQ/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/java14_64/jre/bin/j9vm

-> arg[ 18]: -Dmemory.manager=2048M

-> arg[ 19]: -Xmx2048M

-> arg[ 20]: -Xms2048M

-> arg[ 21]: -DLoadBalanceRestricted=no

-> arg[ 22]: -Djstartup.mode=JCONTROL

-> arg[ 23]: -Djstartup.ownProcessId=1314818

-> arg[ 24]: -Djstartup.ownHardwareId=O0427428665

-> arg[ 25]: -Djstartup.whoami=server

-> arg[ 26]: -Djstartup.debuggable=no

-> arg[ 27]: -DSAPINFO=GSQ_02_server

-> arg[ 28]: -DSAPSTART=1

-> arg[ 29]: -DCONNECT_PORT=64998

-> arg[ 30]: -DSAPSYSTEM=02

-> arg[ 31]: -DSAPSYSTEMNAME=GSQ

-> arg[ 32]: -DSAPMYNAME=GILSAPEQ_GSQ_02

-> arg[ 33]: -DSAPPROFILE=/usr/sap/GSQ/SYS/profile/GSQ_DVEBMGS02_GILSAPEQ

-> arg[ 34]: -DFRFC_FALLBACK=ON

-> arg[ 35]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 36]: -DSAPSTARTUP=1

-> arg[ 37]: -DSAPSYSTEM=02

-> arg[ 38]: -DSAPSYSTEMNAME=GSQ

-> arg[ 39]: -DSAPMYNAME=GILSAPEQ_GSQ_02

-> arg[ 40]: -DSAPDBHOST=GILSAPEQ

-> arg[ 41]: -Dj2ee.dbhost=GILSAPEQ

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

Pls advise.

Thx.

Abdul

[Thr 772] Sun Sep 13 05:02:28 2009

[Thr 772] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [server0]

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

[Thr 3600] Sun Sep 13 05:02:36 2009

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

[Thr 3600] Sun Sep 13 05:02:37 2009

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

[Thr 3600] JLaunchISetClusterId: set cluster id 26770150

[Thr 3600] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 3600] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

[Thr 35212] Sun Sep 13 05:03:27 2009

[Thr 35212] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver

[Thr 35212] Sun Sep 13 05:03:28 2009

[Thr 35212] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI

[Thr 35212] JLaunchIExitJava: exit hook is called (rc = -11113)

[Thr 35212] **********************************************************************

      • 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 35212] SigISetIgnoreAction : SIG_IGN for signal 20

[Thr 35212] JLaunchCloseProgram: good bye (exitcode = -11113)

Accepted Solutions (1)

Accepted Solutions (1)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Have you tried to increase heap memory and restart the server ?

Thanks

Sunny

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

The error message:

[Thr 35212] JLaunchIExitJava: exit hook is called (rc = -11113)

Indicates that one of the core services did not start. The Service Managers controls the life cycle of all services. The services that provide core functionality must always be running. If one of the core services fails to start, the Service Manager exits with an exit code -11113.

To find the name of the core service that failed to start please see the end of the std_server0.out file.

Furthermore the reason why the service failed to start will be evident in the defaultTrace.X.trc file in the server0/log directory.

Regards,

Ventsi Tsachev

Technology Development Support (J2EE Engine)

SAP Labs, Palo Alto, Ca (USA)

Former Member
0 Kudos

Apply the whole SAP note 723909 based on 32 or 64 bit settings at the server and instance level.

Then restart server. Problem should solve.

Former Member
0 Kudos

Hi,

Can you post the developer trace of server0 process which is located in /usr/sap/<SID>/<instance dir.>/j2ee/cluster/server0/log.

Regards

Syed Shoeb Hussaini

Former Member
0 Kudos

It looks like the java VM is starting okay but is bombing during the load process. Have you been able to watch topas (top) while this starts up to see what is happening with the memory?

Have you tried running 'cleanipc 02 remove'? (before starting up).

J. Haynes