Symptom
Netweaver AS Java server nodes restart due to connection issue to Message server and the exceptions below are logged into the traces :
dev_server
JLaunchCloseProgram: good bye (exitcode = -333)
JLaunchCloseProgram: good bye (exitcode = -337)
dev_jcontrol/dev_jstart
LOG Q0I=> NiIRead: P=<IP>:<port>; L=<IP>:<port>: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5082]
ERROR => NiIRead: SiRecv failed for hdl 25/sock 688
dev_ms
ERROR => MsSRead: NiBufReceive (rc=NIECONN_BROKEN) [msxxserv.c 13016]
ERROR => MsSClientHandle: MsSRead C2 (J2EE4042250), MSEINTERN [msxxserv.c 5393]
LOGOUT: J2EE<nodeID> [ipaddress] (UPD )
MsJ2EE_AddDisconnectedNode: add node [nodeID] into disconnect list
there can be issues in multi instance/node servers with broadcast messages from the message server. For example when navigating in NWA > Operations > Start & Stop or NWA > Configuration > Infrastructure > Application Resources:
defaultTrace_xx.xx.trc
An exception occured during invocation of a MBeanServer operation on a remote cluster node. Though the exception is ignored by the caller, the system might be in an inconsistent state. Please check the attached response and stack-trace for the cause of the exception. [ JMX exception (java) v1.0 | | com.sap.engine.services.jmx.exception.JmxConnectorException: Receiving answer for broadcast message failed, from 217468150, timeout 100000, message [ JMX request (java) v1.0 len: 127 | src: cluster req: queryNames params-number: 2 params-bytes: 0 | *:cimclass=SAP_ITSAMJ2eeApplicationInstance,* null ] ]
[EXCEPTION]
com.sap.engine.services.jmx.exception.JmxConnectorException: Receiving answer for broadcast message failed, from 217468150, timeout 100000, message [ JMX request (java) v1.0 len: 127 | src: cluster req: queryNames params-number: 2 params-bytes: 0 | *:cimclass=SAP_ITSAMJ2eeApplicationInstance,* null ]
at com.sap.engine.services.jmx.JmxServiceConnectorServerClusterInvoker.invokeMbs(JmxServiceConnectorServerClusterInvoker.java:128)
...
Caused by: com.sap.engine.frame.cluster.message.ResponseTimedOutException: Participant [217468150] did not return a response in the specified timeout of [100000] ms
#2.0^H#2019 01 21 21:12:04:043#0-500#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C0000AFDD0DD0130000000020000E203#213613551000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendMessage#Administrator#7ED01DEA11E99C9900000CBB7BEF#63b45d551dea11e9877500000cbb7bef#Thread[HTTP Worker [@558942844],5,Dedicated_Application_Thread]#Plain##
java.lang.InterruptedException: No answer in 180000 msec. Listenerkey: 5987, errorKey: 0
at com.sap.engine.core.cluster.impl6.ms.MSNotificationListener.WaitForReply(MSNotificationListener.java:156)#2.0^H#2019 01 21 21:12:04:043#0-500#Warning#com.sap.engine.core.cluster.impl6.ms.MSRawConnection#
#BC-JAS-COR-CLS#kernel.sda#C0000AFDD0DD0130000000020000E203#213613551000000004#sap.com/tc~lm~itsam~ui~mainframe~wd#com.sap.engine.core.cluster.impl6.ms.MSRawConnection.sendMessage#Administrator#7ED01DEA11E99C9900000CBB7BEF#63b45d551dea11e9877500000cbb7bef#Thread[HTTP Worker [@558942844],5,Dedicated_Application_Thread]#Plain##
java.lang.InterruptedException: No answer in 180000 msec. Listenerkey: 5987, errorKey: 0
at com.sap.engine.core.cluster.impl6.ms.MSNotificationListener.WaitForReply(MSNotificationListener.java:156)
Read more...
Environment
- Release Independent
- SAP NetWeaver
Product
Keywords
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 for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.