1622083 - J2EE System fails with "exitcode = -337" | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

1622083 - J2EE System fails with "exitcode = -337"

Symptom

You can see similar errors in the std_dispatcher and std_server logs as below:

Loading: ClusterManager ... [Framework -> criticalShutdown] Exiting Listener Loop. This requires a restart of the node. Possible reason is an interrupted reconnect session to the message server.

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.

...anagerImpl.init(java.util.Properties) [Thread[Thread-1,5,main]] Fatal: Cannot attach to the Message Server. cluster Id is not unique.

Loading: ClusterManager returned false!
Kernel not loaded. System halted.

----------------------------

JLaunchCloseProgram: good bye (exitcode = -337)


Read more...

Environment

SAP NetWeaver Application Server Java

Product

SAP NetWeaver Application Server for Java all versions

Keywords

exitcode, 337, Fatal, Cannot attach to the Message Server, cluster Id is not unique, ClusterManager returned false, Kernel not loaded, System halted, ClusterManager, Framework, criticalShutdown, Listener Loop, interrupted reconnect session to the message server, Socket Listener, -337, NiAcl::checkAddress, deny, no rule matched , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-CST-MS , Message Service , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.