XMII Listerner fails when running XMII in cluster

[Former Member]

We have the same problem mentioned here (no Beans listening for name IDOC_INBOUND_ASYNCHRONOUS).

Our scenario is a SAP MII 12.1 running in cluster.

We followed the "How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener (MII 12.1 to ECC 6.0)" document.

The error occur only when we have the two nodes of the cluster running and we noticed that a few number of IDocs are correctly processed, the major part ends with the error.

We are pretty sure we have followed the documentation and we are lost with this problem. Our last guess was increasing the number of thread when configuring the Resource Adapter.

Can you imagine another cause for this problem?

Here are some log information:

============================================

== Alert                                                                        ==

============================================

          [JRA]ReaderManaged_Application_Thread_15ConfirmTID failed. TID=0A01005A6B1C4FBE258D2D3D. Neither commit no rollback arrived on this node on handle 2, backend confirmed the call

          [JRA]serverExceptionOccurred. Server XMIIIDOC01, Managed_Application_Thread_18, connectionId=8-iridio.cbmm.com.br|sapgw00|XMIIIDOC01, Exception: com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: no Beans listening for name IDOC_INBOUND_ASYNCHRONOUS registered for XMIIIDOC01 on system BORIO02_MIP_01

          [JRA]ReaderManaged_Application_Thread_18, onRollback(), no bean for given tid=0A01005A6B1C4FBE258D2D3D

          [JRA]no Beans listening for name IDOC_INBOUND_ASYNCHRONOUS registered for XMIIIDOC01 on system BORIO02_MIP_01

============================================

== Default Trace                                                            ==

============================================

EndpointActivationImpl.findResourceAdapterByMessageListenerType, Activate: true, MessageListenerType: 'com.sap.mw.jco.jra.AsynchronousMessageListener', MessageEndpointFactory: com.sap.engine.services.ejb3.runtime.impl.MessageEndpointFactoryImpl@70efd290 Application: sap.com/sapjra~xMIIIDOC01, ResourceAdapter: XMIIIDOC01, Error: 

[EXCEPTION]

javax.resource.NotSupportedException: reject registering function  having binding XMII at RA with BindingKey=XMIIIDOC and ProgramId=XMIIIDOC01

at com.sap.mw.jco.jra.JRA$ResourceAdapterImpl.endpointActivation(JRA.java:8784)

at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:531)

at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByMessageListenerType(EndpointActivationImpl.java:256)

at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:88)

at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:59)

at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:95)

at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)

at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:59)

at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:902)

at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:435)

at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:342)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:302)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:479)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocal(ParallelAdapter.java:302)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:863)

at com.sap.engine.services.deploy.server.prl.ParallelApplicationStartTraverser.execute(ParallelApplicationStartTraverser.java:175)

at com.sap.engine.services.deploy.server.prl.ParallelApplicationThread.run(ParallelApplicationThread.java:64)

at com.sap.engine.frame.core.thread.Task.run(Task.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:177)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:295)

Best Regards.

Italo Giovani Stefani

Vetta Group

[agentry_src]

Hi Italo,

Please review the latest Document for configuring the IDoc Listener.  The latest revision addresses some of the reasons for a No Bean... error message. 

But at a guess, it is related to two nodes both asking for delivery of the IDoc concurrently.

Regards, Mike

[Former Member]

Hi Mike.

This is a late response, but we would like to clarify the solution.

It seemed to be a cache problem. We just waited about two weeks and everything is fine until today.

As we have wrongly created two IDocs Listener before and fixed the problem we believe the problem was related to cache. Also, the production environment may have some long cache settings.

Anyway, it is working now!!

Thanks

[agentry_src]

Hi Italo,

Thanks for posting the resolution of your thread!

Regards, Mike