Symptom
In MSCS (Microsoft Cluster Server) environment, the startup of one instance works fine and takes few minutes, but the startup of the second instance:
- it takes a long time to start;
- it hangs in "Starting" status;
- it fails.
Does not matter the sequence (First A and second B, or first B and second A), the J2EE application servers are unable to work together.
Sometimes can be seen the following errors during the startup:
/usr/SAP/<SID>/<INSTID>/work/std_serverX.out:
Service [naming] start ================= ERROR =================
CSN Component [BC-JAS-COR], DC Name [sap.com/naming]
com.sap.engine.frame.ServiceException: JNDI System Exception * Failed to
start the JNDI Registry Service.
...
Caused by: com.sap.engine.frame.cluster.message.
ResponseTimedOutException: Participant [XXXXXX50] did not return a
response in the specified timeout of [100000] ms
/usr/SAP/<SID>/<INSTID>/j2ee/cluster/serverX/log/defaultTraceX.trc:
#2.0##2011 12 21
16:48:40:914#0-200#Warning#com.sap.engine.services.rmi_p4.server#
#BC-JAS-COR-RMT#p4#E41F13905D0D00140000001200001EE0#22327850000001468##c
om.sap.engine.services.rmi_p4.server.ClusterOrganizer.send(int, byte[],
int, int, boolean)
#J2EE_GUEST#0##77A168492C0111E1C82BE41F13905D0D#77a168492c0111e1c82be41f
13905d0d#77a168492c0111e1c82be41f13905d0d#0#Application [13]#Plain##
Exception while sending message to server process XXXXXXX50. The
message will fail if the destination object is not redirectable#
Read more...
Environment
- Windows Server 2008
- SAP NetWeaver Application Server Java
Product
Keywords
MSCS, Windows Server 2008, ERROR => Java node 'server0' terminated with exit code 2150, com.sap.engine.frame.cluster.message.ResponseTimedOutException , KBA , BC-JAS-SF , Startup Framework , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.