SOAP Adapter: Exception in method process

Hello Experts,
We are getting from time to time on the Receiver SOAP Communication Channels the folowing error:
Delivery of the message to the application using connection AFW failed, due to: Exception in method process.
We are getting this error on both types of messages - sync and async.
I did a search on SDN and Notes, but didn't found any description or solution for this error.
Can someone please help with this error?
Thanks in advance!

Here are some details extracted from the log:
Date : 07/30/2008
Time : 8:44:15:783
Message : Error during processing local bean: localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Severity : Error
Category :
Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
Application : sap.com/com.sap.aii.af.app
Thread : output
Datasource : 1217412862462:/usr/sap/xxx/xxx/j2ee/cluster/server1/log/defaultTrace.trc
Message ID : 001CC4B7988E00A5000268B100000CB3000453381549AFAE
Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
Argument Objs :
Arguments :
Dsr Component : xxx
Dsr Transaction : 989219405e0211ddc88b001cc4b7988e
Dsr User : Guest
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
ThreadObject : output
Transaction : SAP J2EE Engine JTA Transaction : [2dffffff91ffffffbdffffffe3040ffffffb0]
User : J2EE_GUEST
Hope this will help somebody to get the clue what is causing this error.

Similar Messages

Xi 3.0: Mail adapter fails with "exception in method process"

Hi.
I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
I tried both async and sync case with the same result. In the sync case, the response contains:

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea???

Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
Anyway, in my server i get a 404 for the link you suggested.
In the async case i don't get any error on the SXMB_MONI but only on the A.F.
I attach the audit log for the async case:
Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
Time Stamp Status Thread ID Sequence No. Description
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
Total: 33 Entries 1020304050 messages displayed per page; this is page 1 of 1 page(s)

Exception in method process

Hi all,
I am configuring a scenario RFC -> XI -> Webservice. In my SOAP adapter trace, i found an error :
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any body please suggest me the possible reasons?
Thanks and best regards,
Kulwant

try this too
com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process
and this
com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process ?
Edited by: Lawrence on Apr 22, 2008 8:17 AM

SOAP Runtime exception: 1023 method IF_SOAP_TRANSPORT_BINDING~receive

SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: HTTP COMMUNICATION FAILURE")
SOAP Runtime exception: 1023 occured in method IF_SOAP_TRANSPORT_BINDING~receive of class CL_SOAP11_HTTP_TPBND at position 1
Getting the error above when making a web service call to external web service. Used to work all the time. Getting the error all the time now.

Hi.
Check the response. Sometimes this error occurs due to an empty response.
Regards.
Rafael Rojas.

XI3.0: SOAP-Adapter Exception

Hi All,
I'm trying to send a message to a web service via the SOAP adapter.
Unfortunately the SOAP adapter throws the following exception:

SOAP: error occured: com.sap.aii.messaging.srt.BubbleException: Failed to call the endpoint: HTTP 0 null [null "null"]; nested exception caused by: java.net.SocketException: Connection timed out:could be due to invalid address

It seems to be that the configured URL does not reach the SOAP adapter.
We use the central J2EE Adapter Engine.
Any hints?
How do I sitch on detailed tracing or logging for the SOAP Adapter? The Audit Log does not contain very much information.
I hope anybody is able to help.
Regards,
Marc

Hi Alessandro,
we solved the problem.
The problem was caused by a firewall. The used port was blocked there. We just reconfigured the firewall and all went fine.
In the meantime I learned somthing about the error message.
"Failed to call the endpoint: HTTP 0 null"
This means that the adapter called the configured endpoint. The "HTTP 0 null" is the result code and error text of the http call. So it returned with error code "0" and it has no associated error text "null".
Another hint that may help you is the OSS note 761921. This note describes how to get an adapter trace.
Hope this reply helps.
Regards,
Marc

SOAP adapter exception

Hi Everyone,
I tried to implement the following scenario SOAP--> XI --> IDOC(R/3). I created all the necessary objects,mapping, Channels. When tried to check the SOAP adapter with http://<hostname>:50000/XISOAPAdapter/MessageServlet?channel=:<service name>:<channelname>, i got the reply as Message STATUS OK.
But when i checked the http://<hostname>:50000/XISOAPAdapter/HelperServlet?action=FindChannel&%20channel=:<service name>:<channelname>. i got the following error
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
- <detail>
- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.SOAP_EXCEPTION</code>
- <text>
- <![CDATA[
java.lang.Exception: invalid channel (party:service:channel) = <null>
at com.sap.aii.af.mp.soap.web.HelperServlet.processFindChannel(HelperServlet.java:364)
Then i used the "MESSAGE Interface" created by SAP to created a new channel and made respective setting. Even then i am getting the same error.
Can any one tell me how to proceed.
Thank you
Bhaskar

Hi Everyone,
It is my mistake, I entered the space between the "Find Channel" and "Channel" in the following URL
http://<hostname>:50000/XISOAPAdapter/HelperServlet?action=FindChannel&%20channel=:<service name>:<channelname>
By removing that it worked fine.
Regards
Bhaskar

Receiver SOAP Adapter Exception

Hi,
I have a SOAP-Receiver set up in directory. Tested the WS using SoapUI 3.5 tool and got a proper response.
Now when i test the same in RWB, i get the following exception:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: Server was unable to process request. ---> Object reference not set to an instance of an object.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checked the Communication Channel monitor, it shows the same error message above but on the 'MessageContent' tab i do not see my payload, instead i only see a soap document.

Actual Payload from RWB,
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_PORequest xmlns:ns0="http://bancousa.com/sapr3/fi/transdata/PegasoFactura">
 <PORequest>
 <RequestCFD version="1.0">
 <Comprobante version="2.0" subTotal="199467.00" total="231381.72" formaDePago="Pago en una sola exhibicion">
 <Emisor rfc="MMM041206JDA">
 </Emisor>
 <Receptor rfc="AMG0608239L9" nombre="AGENCIA MX-5, S.A. DE C.V.">
 <Domicilio calle="BLVD. PEDRO INFANTE" colonia="DESARROLLO URBANO PLAN 3 RIOS" municipio="CULIACAN" estado="SINALOA" pais="MEXICO" codigoPostal="80220" noExterior="2619"/>
 </Receptor>
 <Conceptos>
 <Concepto cantidad="1" noIdentificacion="JM1BL1S50A1256617" descripcion="VALOR DE LA UNIDAD BASICA" valorUnitario="196102.00" importe="196102.00" unidad="PIEZA">
 <Parte cantidad="1" descripcion="AT2-AUTOMATIC TRANSMISSION" valorUnitario="0.00" importe="0.00" unidad="PIEZA">
 </Parte>
 <Parte cantidad="1" descripcion="WHEEL LOCKS" valorUnitario="0.00" importe="0.00" unidad="PIEZA">
 <InformacionAduanera numero="95137889000191" aduana="LAZARO CARDENAS" fecha="2010-04-20">
 </InformacionAduanera>
 </Parte>
 </Concepto>
 <Concepto cantidad="1" descripcion="GASTOS DE TRASLADO" valorUnitario="2200.00" importe="2200.00" unidad="PIEZA">
 </Concepto>
 <Concepto cantidad="1" descripcion="SEGURO DE TRASLADO" valorUnitario="1165.00" importe="1165.00" unidad="PIEZA">
 </Concepto>
 </Conceptos>
 <Impuestos totalImpuestosTrasladados="31914.72">
 <Traslados>
 <Traslado impuesto="IVA" importe="31914.72" tasa="16.00"/>
 </Traslados>
 </Impuestos>
 <Addenda>
 <AddendaEmisor>
 <RequestForPayment>
 <AddendaEmisorFactAuto moneda="MXN" claveVehicular="590108" colorExterior="4K BLANCO CRISTAL PERLADO" colorInterior="B59 NEGRO" financiera="banco FINANCIAL SERVICES" descripcionAuto="2010/BANCO 4 CILINDROS" numSerie="JM6BL15739A1256617" leyendaDocto="PAGO EN UNA SOLA EXHIBICION" noReferenciaInterno="1000000262MX102005" nombreVendedor="BANCO DE MEXICO DE R.L. DE C.V."/>
 </RequestForPayment>
 </AddendaEmisor>
 </Addenda>
 </Comprobante>
 <Transaccion id="1000000262MX102005"/>
 <TipoComprobante nombre="Factura de Autos" clave="EMMV">
 </TipoComprobante>
 <Sucursal nombre="MATRIZ">
 </Sucursal>
 </RequestCFD>
 </PORequest>
</ns0:MT_PORequest>
This is how my payload shows in SoapUI:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:emis="http://www.pegasotecnologia.com/webservices/emision/">
 <soap:Header/>
 <soap:Body>
 <emis:emitirCFD>
 <!Optional:>
 <emis:PoRequestCFD>
 <RequestCFD version="1.0">
 <Comprobante version="2.0" subTotal="199467.00" total="231381.72" formaDePago="Pago en una sola exhibicion">
 <Emisor rfc="MMM041206JDA">
 </Emisor>
 <Receptor rfc="AMG0608239L9" nombre="AGENCIA MX-5, S.A. DE C.V.">
 <Domicilio calle="BLVD. PEDRO INFANTE" colonia="DESARROLLO URBANO PLAN 3 RIOS" municipio="CULIACAN" estado="SINALOA" pais="MEXICO" codigoPostal="80220" noExterior="2619"/>
 </Receptor>
 <Conceptos>
 <Concepto cantidad="1" noIdentificacion="JM1BL1S50A1256617" descripcion="VALOR DE LA UNIDAD BASICA" valorUnitario="196102.00" importe="196102.00" unidad="PIEZA">
 <Parte cantidad="1" descripcion="AT2-AUTOMATIC TRANSMISSION" valorUnitario="0.00" importe="0.00" unidad="PIEZA">
 </Parte>
 <Parte cantidad="1" descripcion="WHEEL LOCKS" valorUnitario="0.00" importe="0.00" unidad="PIEZA">
 <InformacionAduanera numero="95137889000191" aduana="LAZARO CARDENAS" fecha="2010-04-20">
 </InformacionAduanera>
 </Parte>
 </Concepto>
 <Concepto cantidad="1" descripcion="GASTOS DE TRASLADO" valorUnitario="2200.00" importe="2200.00" unidad="PIEZA">
 </Concepto>
 <Concepto cantidad="1" descripcion="SEGURO DE TRASLADO" valorUnitario="1165.00" importe="1165.00" unidad="PIEZA">
 </Concepto>
 </Conceptos>
 <Impuestos totalImpuestosTrasladados="31914.72">
 <Traslados>
 <Traslado impuesto="IVA" importe="31914.72" tasa="16.00"/>
 </Traslados>
 </Impuestos>
 <Addenda>
 <AddendaEmisor>
 <RequestForPayment>
 <AddendaEmisorFactAuto moneda="MXN" claveVehicular="590108" colorExterior="4K BLANCO CRISTAL PERLADO" colorInterior="B59 NEGRO" financiera="banco FINANCIAL SERVICES" descripcionAuto="2010/BANCO 4 CILINDROS" numSerie="JM6BL15739A1256617" leyendaDocto="PAGO EN UNA SOLA EXHIBICION" noReferenciaInterno="1000000262MX102005" nombreVendedor="BANCO DE MEXICO DE R.L. DE C.V."/>
 </RequestForPayment>
 </AddendaEmisor>
 </Addenda>
 </Comprobante>
 <Transaccion id="1000000262MX102005"/>
 <TipoComprobante nombre="Factura de Autos" clave="EMMV">
 </TipoComprobante>
 <Sucursal nombre="MATRIZ">
 </Sucursal>
 </RequestCFD>
 </emis:PoRequestCFD>
 </emis:emitirCFD>
 </soap:Body>
</soap:Envelope>

SOAP Runtime: SOAP Runtime exception: 1023 occurred in method IF_SOAP_TRANS

Hi ,
we currently have the SAP discovery system setup, i have notice that when i check the system log via sm21 , i recieve hundreds of the following error messages:
SOAP Runtime: SOAP Runtime exception: 1023 occurred in method IF_SOAP_TRANSPORT_BINDING~receive of class CL_SOAP11_HTTP_TPBND at position 1
SOAP Runtime: Exception message: SRT: Processing error in Internet Communication Framework: ("ICF Error when receivin g the response: ICM_HTTP_CONNECTION_FAILED")
Please advise where to check on resolving this error as some services donot work because of this,All services start up fine , i have also checked /nsicf and some RFC ,but have not found any thing specific.
Kind Regards
A.

Hi,
I know this question was asked a long time ago but you should check out the following note and fix to un-release the "osp" background jobs running under SM37.
Note 1113842 - Discovery System V3 Central Note

Error in Sender SOAP Adapter on XI 3.0 SP13

Hi All.
I have an application that sends a SOAP message to XI SOAP Adapter, to reach a synchronous interface. I've generated the .wsdl file from the Integration Directory, within the URL:
http://sapbox:59800/XISOAPAdapter/MessageServlet?channel=:BS_PORTAL:CC_S_SOAP_CREDITO
When I try to reach this URL, I get the successful response:
Message Servlet is in Status OK
I've also created the sender SOAP communication channel, fullfilling the default namespace and default interface correctly.
However, when I use wsnavigator client provided by SAP to prove the scenario, the SOAP message doesn't achieve XI, as the XISOAPAdapter EJB throws some exceptions:
HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Sat, 17 Sep 2005 02:59:12 GMT
<?xml version='1.0'?>

<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>BaseEJBException</code>
 <text><![CDATA[
com.sap.aii.af.mp.processor.ModuleProcessorException
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:278)
 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.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:121)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
 ... 19 more
Caused by: java.lang.NoSuchMethodError: com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.setDynamicConfigurationMode(I)V
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createXMBWSBubble(XISOAPAdapterBean.java:1129)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:265)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:562)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 ... 20 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
I've already done something really similar on SP 9. Can it be a new problem from SP13? Does anyone has any idea?
Thanks in advance.
Deise Lima.

Hi Naveen,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy or Altova XML Spy we are getting a 500 internal server error.
Am not sure what causes the error

Receiver SOAP adapter in XI 2.0

We are using receiver SOAP adapter in XI 2.0 and 4.6C R/3 system. Recently we started having this problem when vendor upgraded their webmethod server to post invoices to our XI 2.0. When vendor post 10 invoices to XI and all are posted good in XI but some of invoices give the bad response to the vendor's server as below and vendor's server keep posting the invoices with the bad response until they get good response.
<value name="soapResponseData"><SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: Can't call the endpoint; Exception raised by com.sap.aii.messaging.net.TransportException: response is not an HTTP response</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope></value>
Any help on this is appreciated...
Thanks in advance!
Mrudula

hi,
Check these threads, might be helpful.
Soap Adapter
XI3.0: SOAP-Adapter Exception
Thanks,
Tirumal

Which Adapter to use - HTTP or SOAP Adapter?

Hi Experts,
The third party system will be sending a standard HTTP request with a standard SOAP envelope containing standard XML.
So in this case what adapter I should use HTTP or SOAP?
What is the difference between these two adapters and in which scenarios this should be used?
Thanks.

Hi,
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data using a plain HTTP connection. Depending on the receiver system, outbound messages can be enhanced with certain information.
The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service
servers and the Integration Server or the PCK.
In the SOAP adapter, you can specify security settings to be used to sign/verify the SOAP body.
In addition, you can specify the standard to be used for signing/verifying the SOAP message
whenever Xi need to communicate with any sort of webservice i.e remote applications it uses SOAP adapter..
And XI uses HTTP adapter when you want to post a HTTP request message from a web application to XI.
HTTP Adapter :
1) HTTP Adapter is used by extenal systems to connect to Intergartin server using native HTTP Interface
2) http adapter is a service which is directly connected to integration engine
SOAP Adapter :
1)Allows Local Processing in AAE
2)Exaclty One Operation per Interface
3)Modules for Receiver Adapter
With regards,
Pinangshuk.

Sender Mail Adapter Error: exception caught during processing mail message;

HI , I am configuring mail to file scenario. Need to read mail content (no need to capture From,TO or Subject details) and create a file with the content in the mail.
Need to read mails from microsoft outlook. Exchange server has been configured for POP3 protocol.
Following are the details provoding in sender mail adapter:
URL: provided url in the format: pop://<server name>
Authentication method: plain
provided user credinetions to access mails.
poll interval - 1min
content encoding none.
processing parameters : quality of service-exactly once
Since there is no need to capture From,TO or Subject details, didn't select the option - use mail package.
Verified for unread mails in the mail box and made sure that there are few unread mails.
Also, created data types and other components in IR and completed mapping.
But after starting sender mail communication channel, getting error "exception caught during processing mail message; java.lang.NullPointerException" in RWB-adapter-communication channel monitoring.
please let me know what needs to be done to resolve this error.
Thanks.

HI Stefan, i tried, but still it is giving same error. Yes, i am able to access outlook mail with the user credentials given in the communication channel to access exchange server.
I am using message protocol: xipayload . Also since i dont have to capture TO,from,subject details., created data type just with one element of type string, not in the standard format .Does this makes any difference.

SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processi

Hi: We are using weblogic81 sp3. Other developers in my office ran the same porgram and got no errors.
My startWebLogic.cmd are configured exactly same as theirs.
My startWebLogic classpath:
set CLASSPATH=%WL_HOME%\server\lib\ojdbc14.jar;%WL_HOME%\server\lib\CR122067_81sp3.jar;%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%
I keep getting this webservice error.
SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processing: w
eblogic.xml.schema.binding.DeserializationException: mapping lookup failure. typ
e=['java:language_builtins.util']:ArrayList schema context=TypedSchemaContext{ja
vaType=[Ljava.lang.Object;} (see Fault Detail for stacktrace)
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webse
rvice/fault/1.0.0">weblogic.xml.schema.binding.DeserializationException: mapping
lookup failure. type=['java:language_builtins.util']:ArrayList schema context=T
ypedSchemaContext{javaType=[Ljava.lang.Object;}
at weblogic.xml.schema.binding.RuntimeUtils.lookup_deserializer(RuntimeU
tils.java:461)
thank you for your help

we used castor to do xml mapping

Soap receiver adapter exception

Hi,
I am using SOAP receiver adapter to access a web service that is hosted on SAP Web AS (in this case it is the integration server Web AS). I use the web services navigator to test the web service and the web service works fine. The name of the web service is 'RemoteCrossReferenceProcessor' and it has one operation 'crossReference'.
But with the soap adapter, I am getting OperationNotFoundException in the logs and my web service is not getting accessed. Here is the server log:
An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:RemoteCrossReferenceProcessor'; Key name:'SoapRequestWrapper' key value:'crossReference'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
#1.5#0003BA0FF9EA0022000000840000688D0003F9349A3C2D61#1118429251382#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######b40aca80d9be11d994360003ba0ff9ea#SAPEngine_System_Thread[impl:5]_47##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:#http://sapsand1:8000/sap/xi/engine?type=entry#
Here is adapter configuration:
Transport Protocol:HTTP
Message Protocol:SOAP 1.1
Adapter Engine:Integration Engine
Target URL: http://<server_name>>:50000/RemoteCrossReferenceProcessor/Config?style=document
User:
Password:
Default SOAP Action:
I imported the WSDL into the external definition and used the messages from the WSDL for defining my interface mappings.
I am using XI 3.0 SR1 (SP 09).
I am out of ideas as to why the SOAP adapter is not calling my web service. Please help me with your suggestions.
Thanks and Regards.

HI Dani,
I was looking for this error and I found this post AXIS SOAP Receiver. This post says about other errors, but sugests many ideas to found the soluction, like:
1- non-deployed all AXIS jars; (but in this case it deployed all)
2- Exists this note for one erro in AXIS: (https://service.sap.com/sap/support/notes/1028961).
3- this document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f) that have sets for header parameters. This is interesting becouse one of this parameters is obligatory but isn't filled, can occur error like "null object".
By the way, you can check if have update to AXIS (http://ws.apache.org/axis/), becouse isn't a SAP application and in other systems can have this error.
I hope this helps,
Romerito Silva

SOAP Fault Exception: method not found

Hi,
I've tried to consume a web service (written in Java) in ABAP using a generated client proxy with logical port. I receive return code 500 and a fault exception like "method for requestMethod was not found".
Has anyone a hint?
Thanks in advance,
Daniel

I have not seen that error before, but my first suggestion would be to state the obvious - check your logical port definition and make sure that the settings are correct, i.e., that they match the WSDL document. You'll want to check that the SOAP Action on the Operations tab is correct and that the URL for the web service is correct on the Call Parameters tab.

SOAP Adapter: Exception in method process

Similar Messages

Maybe you are looking for