on 03-21-2009 3:14 AM
DEAR MASTERS
after configuring SLD on integerated ABAP+JAVA server0 not starting
**********************************************************************
trc file: "D:\usr\sap\W55\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
-
node name : ID9278150
pid : 4140
system name : W55
system nr. : 00
started at : Sat Mar 21 08:45:23 2009
arguments :
arg[00] : D:\usr\sap\W55\DVEBMGS00\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
arg[02] : -DSAPINFO=W55_00_server
arg[03] : pf=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
arg[04] : -DSAPSTART=1
arg[05] : -DCONNECT_PORT=1060
arg[06] : -DSAPSYSTEM=00
arg[07] : -DSAPSYSTEMNAME=W55
arg[08] : -DSAPMYNAME=wipro5_W55_00
arg[09] : -DSAPPROFILE=D:\usr\sap\W55\SYS\profile\W55_DVEBMGS00_wipro5
arg[10] : -DFRFC_FALLBACK=ON
arg[11] : -DFRFC_FALLBACK_HOST=localhost
JHVM_BuildArgumentList: main method arguments of node [server0]
**********************************************************************
[Thr 4668] Sat Mar 21 08:58:30 2009
[Thr 4668] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 4668] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 4668] JLaunchISetClusterId: set cluster id 9278150
[Thr 4668] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 4668] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 4428] Sat Mar 21 08:59:58 2009
[Thr 4428] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 4428] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
[Thr 4616] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 4616] **********************************************************************
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.
Hi,
If you configured your JAVA server to refer ABAP as its UME, the problem is probably caused by wrong configuration of connection to the ABAP system. And if the server could not connect to UME, it wouldn't start.
You can check the defaultTrace, it usually gives an exact description of the problem.
Hope it helps,
Anna.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Also please check the following SAP note:
Note 940893 - Analysis of errors within the startup of J2EE Engine 6.40
I hope it helps
Regrads
Chen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please find the link below for J2EE start up problem.
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d396d]
Please refer to following note for VM settings.
[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=723909]
Please also check the license validity on this server.
Hope this helps.
Manoj Chintawar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
I have moved this thread to the Netweaver Administrator forum. You have a better chance of getting an answer to your query if you open it in the correct forum. I think the Netweaver Administrator is the best forum for this issue.
Regards
Mark Smyth
XI/PI Moderator
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.