SAP Knowledge Base Article - Preview

2569214 - IDoc Adapter Monitor: Metadata Monitor timeout error

Symptom

 You try to open the IDoc Adapter Monitor: Metadata Monitor but after a few minutes you get the following error:

Caused by: com.sap.engine.services.jmx.exception.MBeanServerClusterException: Exception during invocation of remote MBeanServer method, target node: 3670751
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:816)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.invoke(ITSAMUIMBeanServerConnectionWrapper.java:379)
at com.sap.tc.lm.itsam.ui.proxy.JMXGenericModelClassMBean.invokeOperation(JMXGenericModelClassMBean.java:610)
... 75 more
Caused by: com.sap.engine.services.jmx.exception.JmxConnectorException: Sending message synchronously failed, target node 3670751, message [ JMX request (java) v1.0 len: 2902 | src: cluster target-node: 3670751 req: invoke params-number: 4 params-bytes: 0 | com.sap.default:SAP_J2EEClusterNode=3670751,SAP_ITSAMXIIDOCMetadataService.SystemCreationClassName=SAP_ITSAMXIIDOCMetadataService,SAP_ITSAMXIIDOCMetadataService.Name=SAP_ITSAMXIIDOCMetadataService,cimclass=SAP_ITSAMXIIDOCMetadataService,type=SAP_ITSAMJ2eeCluster.SAP_ITSAMXIIDOCMetadataService,SAP_ITSAMXIIDOCMetadataService.CreationClassName=SAP_ITSAMXIIDOCMetadataService,SAP_ITSAMXIIDOCMetadataService.SystemName=SAP_ITSAMXIIDOCMetadataService,SAP_ITSAMJ2eeCluster.Name=<SID>.SystemHome.<HOSTNAME>,SAP_ITSAMJ2eeCluster.CreationClassName=SAP_ITSAMXIIDOCMetadataService,version=3.0 RetreiveIDOCMetadata [Ljava.lang.Object;@245281e4 [Ljava.lang.String;@5c6d893 ]
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(MBeanServerConnectionImpl.java:672)
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invoke(MBeanServerConnectionImpl.java:459)
at com.sap.engine.services.jmx.MBeanServerConnectionSecurityWrapper.invoke(MBeanServerConnectionSecurityWrapper.java:221)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
... 78 more
Caused by: com.sap.engine.frame.cluster.message.ResponseTimedOutException: Participant [3670751] did not return a response in the specified timeout of [100000] ms
at com.sap.engine.core.cluster.impl6.p2pnio.P2PMessageRequestSend.waitForAnswer(P2PMessageRequestSend.java:226)
at com.sap.engine.core.cluster.impl6.p2pnio.P2PConnectorImpl.sendRequest(P2PConnectorImpl.java:256)
at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendRequest(ClusterManagerImpl.java:2866)
at com.sap.engine.core.cluster.MessageContextImpl.sendAndWaitForAnswer(MessageContextImpl.java:66)
at com.sap.engine.services.jmx.JmxFrame.sendAndWaitForAnswer(JmxFrame.java:839)
at com.sap.engine.services.jmx.JmxServiceConnectorServerInvoker.invokeMbs(JmxServiceConnectorServerInvoker.java:47)
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(MBeanServerConnectionImpl.java:666)
... 81 more


You collect thread dumps while opening the IDoc Adapter Monitor: Metadata Monitor and notice similar threads:

"HTTP Worker [@1356426529]" #147 prio=5 os_prio=64 cpu=44845.00 [reset 176.90] ms elapsed=211366.11 [reset 86.57] s allocated=2083931368 B (1.94 GB) [reset 3493360 B (3.33MB)] defined_classes=1868
io= file i/o: 83514009/371742 B, net i/o: 7414520/4071621 B, files opened:226, socks opened:35 [reset file i/o: 118332/0 B, net i/o: 45662/5047 B, files opened:5, socks opened:0 ]
user="J2EE_ADMIN" session="-1849795546" request="114370" application="sap.com/tc~lm~itsam~co~ui~xi~idoc~wd" isapplicationthread="true" tid=0x0000000005a66000 nid=0xab / 171 lwp-id=171 in Object.wait() [_thread_blocked (_at_safepoint), stack(0xfffffd7ec6200000,0xfffffd7ec6400000)] [0xfffffd7ec63fc000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(J)V(Native Method)
- waiting on <0xfffffd7f16524da8> (a com.sap.engine.core.cluster.impl6.p2pnio.P2PMessageRequestSend)
at com.sap.engine.core.cluster.impl6.p2pnio.P2PMessageRequestSend.waitForAnswer(IJ)Lcom/sap/engine/frame/cluster/message/MessageAnswer;(P2PMessageRequestSend.java:186)
- locked <0xfffffd7f16524da8> (a com.sap.engine.core.cluster.impl6.p2pnio.P2PMessageRequestSend)
at com.sap.engine.core.cluster.impl6.p2pnio.P2PConnectorImpl.sendRequest(III[BIIJ)Lcom/sap/engine/frame/cluster/message/MessageAnswer;(P2PConnectorImpl.java:256)
at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendRequest(III[BIIJ)Lcom/sap/engine/frame/cluster/message/MessageAnswer;(ClusterManagerImpl.java:2866)
at com.sap.engine.core.cluster.MessageContextImpl.sendAndWaitForAnswer(II[BIIJ)Lcom/sap/engine/frame/cluster/message/MessageAnswer;(MessageContextImpl.java:66)
at com.sap.engine.services.jmx.JmxFrame.sendAndWaitForAnswer(II[BIIJ)Lcom/sap/engine/frame/cluster/message/MessageAnswer;(JmxFrame.java:839)
at com.sap.engine.services.jmx.JmxServiceConnectorServerInvoker.invokeMbs(Lcom/sap/engine/services/jmx/RequestMessage;)Lcom/sap/engine/services/jmx/ResponseMessage;(JmxServiceConnectorServerInvoker.java:47)
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invokeMbsInternal(Lcom/sap/engine/services/jmx/RequestMessage;)Ljava/lang/Object;(MBeanServerConnectionImpl.java:666)
at com.sap.engine.services.jmx.MBeanServerConnectionImpl.invoke(Ljavax/management/ObjectName;Ljava/lang/String;[Ljava/lang/Object;[Ljava/lang/String;)Ljava/lang/Object;(MBeanServerConnectionImpl.java:459)
at com.sap.engine.services.jmx.MBeanServerConnectionSecurityWrapper.invoke(Ljavax/management/ObjectName;Ljava/lang/String;[Ljava/lang/Object;[Ljava/lang/String;)Ljava/lang/Object;(MBeanServerConnectionSecurityWrapper.java:221)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(Lcom/sap/pj/jmx/server/interceptor/InvocationContext;Ljavax/management/ObjectName;Ljava/lang/String;[Ljava/lang/Object;[Ljava/lang/String;)Ljava/lang/Object;(ClusterInterceptor.java:813)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(Ljavax/management/ObjectName;Ljava/lang/String;[Ljava/lang/Object;[Ljava/lang/String;)Ljava/lang/Object;(MBeanServerInterceptorChain.java:367)
at com.sap.lm.itsam.ui.connection.impl.ITSAMUIMBeanServerConnectionWrapper.invoke(Ljavax/management/ObjectName;Ljava/lang/String;[Ljava/lang/Object;[Ljava/lang/String;)Ljava/lang/Object;(ITSAMUIMBeanServerConnectionWrapper.java:379)
at com.sap.tc.lm.itsam.ui.proxy.JMXGenericModelClassMBean.invokeOperation(Ljava/lang/String;[Ljava/lang/Object;[Ljava/lang/String;)Ljava/lang/Object;(JMXGenericModelClassMBean.java:610)
at com.sap.tc.lm.itsam.ui.proxy.JMXAbstractModelClass.invokeOperation(Ljava/lang/String;[Ljava/lang/Object;[Ljava/lang/String;)Ljava/lang/Object;(JMXAbstractModelClass.java:159)
at com.sap.tc.lm.itsam.co.ui.xi.idoc.wd.idocmonmodel.SAP_ITSAMXIIDOCMetadataService.RetreiveIDOCMetadata(Lcom/sap/tc/lm/itsam/co/ui/xi/idoc/wd/idocmonmodel/SAP_ITSAMXIIDOCMDataSearch;JJ)Lcom/sap/tc/lm/itsam/co/ui/xi/idoc/wd/idocmonmodel/SAP_ITSAMXIIDOCMData;(SAP_ITSAMXIIDOCMetadataService.java:112)
at com.sap.tc.lm.itsam.co.ui.xi.idoc.idocmetadatacomp.IDocMetaDataComp.getAllIDocMessages()V(IDocMetaDataComp.java:687)
at com.sap.tc.lm.itsam.co.ui.xi.idoc.idocmetadatacomp.IDocMetaDataComp.wdDoInit()V(IDocMetaDataComp.java:214)
at com.sap.tc.lm.itsam.co.ui.xi.idoc.idocmetadatacomp.wdp.InternalIDocMetaDataComp.wdDoInit()V(InternalIDocMetaDataComp.java:520)


Read more...

Environment

  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver 7.5

Product

SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

IDoc Adapter Monitor, Metadata Monitor, IDoc Adapter Monitor : Metadata Monitor, IDOC_AAE, RFC destination, JavaIdocAdapter, Resource Adapter, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.40, PI 7.40, PO 7.40, Process Orchestration 7.50, PI 7.50, PO 7.50, NetWeaver, XI , KBA , BC-NWA-XPI , Process Integration (PI) Monitoring , BC-XI-CON-IDO , Idoc Adapter J2EE , 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.