Hi All,
SAP J2EE engine went down after performing database refresh from prod to non prod system in PI7.0. We have followed the sap note 1622083 - J2EE System fails with "exitcode = -337" not useful for our issue.Please find the detailed error message below.
Fri Apr 17 08:05:05 2015
(CompilerOracle read from file /usr/sap/FXS/DVEBMGS33/exe/sapjvm_4/jre/.hotspot_compiler)
[Thr 772] Fri Apr 17 08:05:07 2015
[Thr 772] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [dispatcher]
**********************************************************************
[Thr 7198] Fri Apr 17 08:05:13 2015
[Thr 7198] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
[Thr 7198] JHVM_RegisterNatives: 8 of 9 methods in com.sap.bc.krn.perf.PerfTimes registered.
[GC 286016K->2420K(2065408K), 0.0971680 secs]
[Thr 7198] Fri Apr 17 08:05:14 2015
[Thr 7198] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.JStartupFramework
[Thr 7198] JLaunchISetClusterId: set cluster id 339479400
[Thr 3856] JLaunchIExitJava: exit hook is called (rc = -337)
[Thr 3856] **********************************************************************
[Thr 3856] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 3856] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 3856] *** for additional information and trouble shooting.
[Thr 3856] **********************************************************************
[Thr 3856] SigISetIgnoreAction : SIG_IGN for signal SIGCHLD
[Thr 3856] JLaunchCloseProgram: good bye (exitcode = -337)
stdout/stderr redirect
--------------------------------------------------------------------------------
node name : dispatcher
pid : 19202134
system name : FXS
system nr. : 33
started at : Fri Apr 17 07:18:52 2015
[Thr 01] MtxInit: 10000 0 2
(CompilerOracle read from file /usr/sap/FXS/DVEBMGS33/exe/sapjvm_4/jre/.hotspot_compiler)
SAP J2EE Engine Version 7.00 SP 29 PatchLevel 121396.450 is starting...
Loading: LogManager ... 671 ms.
Loading: PoolManager ... 3 ms.
Loading: ThreadManager ... [GC 286016K->2415K(2065408K), 0.0368430 secs]
133 ms.
Loading: IpVerificationManager ... 12 ms.
Loading: ConnectionsManipulator ... 37 ms.
Loading: ClassLoaderManager ... 29 ms.
Loading: ClusterManager ... [Framework -> criticalShutdown] Exiting Listener Loop. This requires a restart of the node. Possible reason is an interrupted reconnect sess
ion to the message server.
Apr 17, 2015 7:18:57 AM com.sap.engine.core.Framework [SAP J2EE Engine|MS Socket Listener] Fatal: Critical shutdown was invoked. Reason is: Exiting Listener
Loop. This requires a restart of the node. Possible reason is an interrupted reconnect session to the message server.
Please advise us to fix this issue.
Regards,
MK