on 10-21-2005 1:57 PM
Hi friends,
I have a nasty XI problem. Whenever I want to post a message (it doesn't matter which scenario) I get the error message:
Delivery of the message to the application using connection AFW failed,
due to: Couldn't find delivery channel for message:
5a93a5a0-4230-11da-b278-001279d35a7b. Setting message to status failed.
Error category: XI_J2EE_ADAPTER_ENGINE
Error code: CHANNEL_DETERMINATION_FAILED
I have rebooted XI, I did a CPA cache refresh, I recreated the scenario's, nothing works...
TIA
Message was edited by: Peter Delve
The following might be a solution for your problem.
The CHANNEL_DETERMINATION_FAILED error is typically caused when one is trying to test his/her message in the <b>RWB/Adapter Engine</b> instead of the <b>RWB/Integration Engine</b>.
Start the Runtime Workbench > Component Monitoring > Integration Server > Integration Engine > Test Message.
I hope this helps (it did for me),
Danny De Roovere.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Even I am facing the same problem in our XI system. Checked CPA Cache - that seems alright. The interface name is also not too long. Do you guys learnt something in your case that could help me?
Thanks,
Deepthi.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you guys figure this out. I have the similar weird problem.
My two SOAP scenarios are working and the third is not. I have tried all kinds of permuntations and combinations including recreation of the whole scenario. The scenario was working before I changed the sender soap communication channel.
I have played around with the Receiver Determination but to no avail.
I get the following error in XMLSPY
<?xml version="1.0"?>
<!-- see the documentation -->
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>DeliveryException</code>
<text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:879)
at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:508)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:418)
at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:125)
at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:511)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
]]></text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
In the SXMB_MONI I get the system error which points to the Receiver Determination and in the trace there is a entry which looks like
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="1" type="T">No Relation found - accept given receivers.</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
Indicating that the interface was not able to determine the Receiver. Whereas in the Test configuration everything looks fine and all green.
Any clues.
Thanks
Pradeep
The following might be a solution for your problem.
The CHANNEL_DETERMINATION_FAILED error is typically caused when one is trying to test his/her message in the <b>RWB/Adapter Engine</b> instead of the <b>RWB/Integration Engine</b>.
Start the Runtime Workbench > Component Monitoring > Integration Server > Integration Engine > Test Message.
I hope this helps (it did for me),
Danny De Roovere.
Hi Peter,
We found the problem!!!!
Your message interface name is too long.
Try and let me know.
Greetz,
Rene
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Peter I'm having the same issue!
I'm also not new to XI and haven't had this problem before.
Tried the same things you did (and more)
Can someone help us on this issue?
TIA
René Jaspers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter
You have already couple of suggestions which normally works.
I guess you should check your receiver agreement, i.e your receiver channel.
RWB --> Component monitoring --> Adapter monitoring --> your receiver channel (it should be green).
If it is not, then thats where the problem lies.
Also there is a nice link for Problem Analysis Guide, which tells you the approach to take to analyse a problem,
http://help.sap.com/saphelp_nw04/helpdata/en/6c/7ffb3f6c78ee28e10000000a1550b0/frameset.htm
cheers
Sameer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.