XI3 Soap Adapter DeliveryException

[Former Member]

Hi,

When sending a SOAP message to the defined SOAP communication channel, we receive "failed to call aadpter engine" with DeliveryException for HTTP 404.

Anybody knows what causes it and how can it be fixed?

Here's the full exception dump:

<?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>failed to call the adapter engine</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:697)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)

at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:513)

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:385)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

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:94)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404.

at com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:122)

at com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)

at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)

at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)

... 20 more

Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404.

at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:156)

at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:419)

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

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

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

]]>

</text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

[JiriEhrlich · Accepted solution]

Hi Avihai,

1) Test SOAP service and connectivity from non-SAP SOAP client (you can use HTML page for instance) or better from J2EE WS client

(http://<xi_host>:<j2ee_port>/wsnavigator/enterwsdl.html)

2) Check SOAP Adapter status http://xi_host>:<j2ee_port>/AdapterFramework

3) Check Adapter log:

Runtime Workbench -> Message Monitoring -> af.<host> -> Display -> Start

Jiri

[Former Member]

Hi Avihai,

We are also getting same problem. Please highlight on this, if you have already solved?

Thanks,

Regards,

Rohit

[Former Member]

Hi Rohit,

Apparently the problem here was a wrong definition of the Integration Engine in the SLD, which was set to use port 50000 instead of 8000.

The monitors do supply good aid, just have to notice those small details...

Hope this helps,

Cheers