on 12-16-2009 12:32 PM
Hi SAP Java Experts,
We recently installed 7.1 CE EHP1 with Oracle 10.2.0.4.for a SAP MII project. The system ran fine for two weeks, but now when we try to start the Java instance, the jstart process hangs and server0 never starts.
The tail of the developer trace file looks like this:
F [Thr 3532] Wed Dec 16 11:33:32 2009
F [Thr 3532] *** LOG => Signal 13 SIGCHLD.
F [Thr 4464] *** LOG => Process server0 stopped (pid 5960).
*F [Thr 4464] *** WARNING => Node server0 failed: result 2, exit code -1501. [sfxxnode.hpp 1005]*
F ********************************************************************************
F Java process [collector] properties:
F section name : collector
F config file : S:\usr\sap\ERT\J00\exe\startup.properties
F node name : collector
F home directory : S:\usr\sap\ERT\J00/j2ee
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F ********************************************************************************
F Starting process: S:\usr\sap\ERT\J00\exe\jstart.EXE
F arg[ 1] = -nodeId=1002
F arg[ 2] = pf=S:\usr\sap\ERT\SYS\profile\ERT_J00_gbebpmesmiis
F arg[ 3] = -DSAPINFO=ERT_00_collector
F arg[ 4] = -hostvm
F arg[ 5] = -nodeName=collector
F arg[ 6] = -file=S:\usr\sap\ERT\J00\exe\startup.properties
F arg[ 7] = -jvmFile=S:\usr\sap\ERT\J00\work\jstart.jvm
F arg[ 8] = -traceFile=S:\usr\sap\ERT\J00\work\dev_collector
F arg[ 9] = -javaOutFile=S:\usr\sap\ERT\J00\work\jvm_collector.out
F arg[10] = -clusterId=ID8222850
F arg[11] = -exitcode
F arg[12] = -1501
F exePath : PATH=S:\usr\sap\ERT\J00\exe\sapjvm_5\bin;S:\usr\sap\ERT\J00\exe;D:\oracle\ETH\102\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
F libPath : PATH=S:\usr\sap\ERT\J00\exe\sapjvm_5\jre\bin\server;S:\usr\sap\ERT\J00\exe\sapjvm_5\jre\bin;S:\usr\sap\ERT\J00\j2ee\os_libs;S:\usr\sap\ERT\J00\exe\sapjvm_5\bin;S:\usr\sap\ERT\J00\exe;D:\oracle\ETH\102\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
F stdout : S:\usr\sap\ERT\J00\work\std_collector.out
F stderr : S:\usr\sap\ERT\J00\work\std_collector.out
F console : no
F debugger: no
F nice : no
F ********************************************************************************
F Process collector started with pid 1400
F ********************************************************************************
F [Thr 4464] *** LOG => Process collector started (pid 1400).
F
F [Thr 4464] Wed Dec 16 11:33:48 2009
F [Thr 4464] *** LOG => Process collector stopping (pid 1400).
F
F [Thr 4168] Wed Dec 16 11:33:48 2009
F [Thr 4168] *** LOG => Signal 13 SIGCHLD.
F [Thr 4464] *** LOG => Process collector stopped (pid 1400).
F [Thr 4464] *** LOG => Removing enque locks for ID 8222850.
F [Thr 4464] *** LOG => Instance state is "Some processes running" (RUNNING @ 0, INACTIVE).
The only obvious error in the trace file is on the 4th line down, which states:
*F [Thr 4464] *** WARNING => Node server0 failed: result 2, exit code -1501. [sfxxnode.hpp 1005]*
I've searched everywhere I can think of (OSS, SDN, Google, colleagues) for an answer, but cannot find anything. All I can find is that it's a framework error and probably down to a manager not starting. How do I tell which manager is causing the failure?
Can anyone help?
Kind regards,
Arwel Owen
Princes Ltd
Liverpool, UK.
Edited by: Arwel Owen on Dec 16, 2009 1:32 PM
Can you please check what is the webservice version you are using and if itu2019s same as another components deployed?
If the version is different, please deploy new version of the webservice.sda.
It is part from ENGINEAPI<(><<)>X>.SCA.
I would ask you to put webservice.sda (710_SPx) in the
/usr/sap/<>/<>/j2ee/cluster/bootstrap/scripts directory.
Best Regards
Sajjan Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sajjan,
I am also facing the same issue that java server0 is not coming up with -1501 error with:
"
ERROR: Server process failed to start due to:
com.sap.engine.frame.ServiceRuntimeException: Interface webservices has provider webservices and can not set tc~je~webservices~srv as provider."
As you suggested to check the version of ENGINEAPI<(><<)>X>.SCA., but how to check the version of the component, JSPM is also not working.
I am not sure where else can we find the component version details.
I request you to please provide detailed steps to resolving this problem completely.
Thanks to revert.
Regards,
Prajakta Patkar
Sorry about the formatting of the last message. It looked great during editing!!!! Arwel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Denish,
Here is the std_server0.out log (I hope it's readable):
Reading kernel properties from kernelProperties.bin file...
Checked the data for 31 ms
Read the objects for 172 ms
Substituted the values for 15 ms
Finished reading kernel objects for 187 ms
Startup mode [NORMAL] and action [NONE] read
AS Java version [7.11.3710.48555.20090609090212] is starting server process [ID8222850] on host [gbebpmesmiis]...
Loading [LogManager]... [94] ms
Loading [PoolManager]... [0] ms
Loading [ApplicationThreadManager]... [78] ms
Loading [ThreadManager]... [16] ms
Loading [ClassLoaderManager]... [31] ms
Loading [ClusterManager]... [360] ms
Loading [LockingManager]... [62] ms
Loading [ConfigurationManager]... [GC [ParNew: 139776K->7259K(209664K), 0.0184660 secs] 139776K->7259K(1606400K), 0.0185867 secs]
[1609] ms
Loading [CacheManager]... [63] ms
Loading [DatabaseManager]... [375] ms
Loading [SessionManager]... [266] ms
Loading [LicensingManager]... [31] ms
Loading [ServiceManager]...
Initialize components for : 203 ms.
ERROR: Server process failed to start due to:
com.sap.engine.frame.ServiceRuntimeException: Interface webservices has provider webservices and can not set tc~je~webservices~srv as provider.
at com.sap.engine.core.service630.container.InterfaceWrapper.setServiceProviderName(InterfaceWrapper.java:80)
at com.sap.engine.core.service630.container.ReferenceResolver.initDeclaredInterfaceProvidersForService(ReferenceResolver.java:104)
at com.sap.engine.core.service630.container.ReferenceResolver.initDeclaredInterfaceProviders(ReferenceResolver.java:94)
at com.sap.engine.core.service630.container.ReferenceResolver.resolveComponentReferences(ReferenceResolver.java:70)
at com.sap.engine.core.service630.container.MemoryContainer.start(MemoryContainer.java:249)
at com.sap.engine.core.service630.container.ServiceContainerImpl.init(ServiceContainerImpl.java:139)
at com.sap.engine.core.Framework.loadSingleManager(Framework.java:630)
at com.sap.engine.core.Framework.loadManagers(Framework.java:394)
at com.sap.engine.core.Framework.start(Framework.java:329)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.boot.FrameThread.startFramework(FrameThread.java:155)
at com.sap.engine.boot.FrameThread.run(FrameThread.java:179)
at com.sap.engine.boot.StartFrame.work(StartFrame.java:93)
at com.sap.engine.boot.Start.main(Start.java:35)
Many thanks,
Arwel.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.