Receiver SOAP - Delivery Exception

Hi,
My scenario is RFC to SOAP.
The problem is in SOAP receiver adpater.
The url and all connection parameters are correct and the scenario is working fine.
But some times the response from SOAP service is like
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Software caused connection abort: recv failed; HTTP 200 OK</SAP:AdditionalText>
The SOAP server is running all the time.
Is it due to connection problem?
Any idea?
Thanks,
Uma
Message was edited by:
Uma Maheswari

I hope you have seen this blog for HTTP errors
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Similar Messages

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>

Java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize

Hi All,
I am getting this exception while invoking one of our service from EM. Any pointers will be very helpful.
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:813) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:385) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:303) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:187) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1491) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:111) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:384) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:114) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:101) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:111) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:384) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:114) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:95) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:972) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:439) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:219) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:102) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:211) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:131) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:447) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:181) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:183) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:419) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:61) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3739) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3705) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2282) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2181) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1491) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Failure in SDOSerializer.deserialize. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:362) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:1004) at

Hi,
its JDeveloper and ADF on this forum. For EM related questions, you should try the EM forum
Frank

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.

Receiver SOAP : Parsing SOAP Exception

Hello
We have a simple scenario SOAP scenario and we are calling backend service in our Receiver SOAP
It seems that issue is with the SOAP Action.
Our backend service has multiple SOAP Actions :
Endpoint is as follows
http://serverID/ABCSoftware/ABCdataexchange.asmx
The SOAP Action is given as follows
http://ABCSoftware.net/SOAPAction
We are getting the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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: System.Web.Services.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (1, 266). ---> System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at System.Xml.XmlConvert.ToInt32(String s) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read40_Item(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read141_AllocatedResourceDetails() at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer172.Deserialize(XmlSerializationReader reader) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) --- End of inner exception stack trace --- at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle) at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() --- End of inner exception stack trace --- at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We appreciate your assistance with the issue.
Thanks.
Kiran

Hi Kiran
As you have multiple SOAP action. WSDL can have only one and can be used per communication channel.
Looking at your error its a XML serialization issue - exception with parser. Your XML input is not correct. If changes are made in your system / target system for the WSDL used. Reimport corrected one and try again
Thanks
Gaurav

RFC to SOAP Scenario -- Delivery Exception

Hi All,
I am working on RFC to SOAP scenario.
On executing a program in the SAP system, the system is throwing a dump stating "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML".
I feel that the error is because of the response not being sent back by the webservice. On executing the webservice independently, it is working fine i.e. sending back the response.
Can anyone suggest the possible reasons for this error and what needs to be done to rectify this?
Thanks,
Ravi Kiran

the return from the Web service must have been an HTML(may be an error page or something)...What kind of authorization does this WS look for ?
Pls check these threads...
SOAP Receiver Adapter Proxy Settings
Receiver SOAP Adapter Error: invalid content type for SOAP: TEXT/HTML

Error in applying security settings in Receiver SOAP Adapter

Hi,
I've used Web Services Security (Oasis standard) and the digital signature and encryption certificate in receiver SOAP adapter and the corresponding Sender Agreement, for adding digital signature and encrypting the message. While sending the message we are getting an error in the adapter engine as below. If anyone can throw light on this it'll be highly appreciated :
2008-07-18 17:00:21 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: SAXException in Method: run().. To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii.af.security.impl.exception.MessageSecurityException: SAXException in Method: run()..
2008-07-18 17:00:21 Error Exception caught by adapter framework: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXException in Method: run().; To-String: com.sap.aii
2008-07-18 17:00:21 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: ApplyMessageLevelSecurity.run(). AccessControlException. Please check that your Code has the XiSecurityRuntimePermission.Context: com.sap.aii.af.security.impl.exception.MessageSecurityException: Exception in Method: apply( Message, CPALookupObject ). General exception, no further informations. Message: MessageSecurityContext in Method: apply( Message, CPALookupObject ). ApplyThread-Exception Message: SAXExce.
Thanks,
Dipankar

hi dipanker,
check the note 856597
its usefull
regards
kummari

Error in Adapter engine of receiver soap adapter

Hi All,
There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
Below is the description i am getting in audit logs.
Success SOAP: completed the processing
Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
Error The message status set to NDLV.
Moreover this is a production issue and interface was running fine till last friday.
Has someone ever faced this issue ?
Please provide your valuable inputs on this.
Thanks
Anku

Hi,
Search in sdn with your error message string,you will find ton of links.
HTTP401 error occurs for many reasons.
still no solution let us know..
Regards,
Raj

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.

Delivery Exception

Hi all,
I am trying to connect to Siebel server throuh iWay Siebel Adapter. It is showing following delivery exception in SXMB_MONI.
com.sap.aii.af.ra.ms.api.DeliveryException: IWAY AFJCA SAPXI cannot process the message via call. Location info is missing for the request
Could anybody help me to solve this issue?
Thanks & Regards,
sekhar

Hi Krishna,
Try this thread..
DeliveryException:: invalid content type for SOAP: TEXT/HTML
SSL Configuration on Visual Administrator (for XI Receiver Soap Adapter)
Web Services error message ! !??
Hope it helps you!
cheers,
Prashanth

Err "Couldn't retrieve binding for the given channelId" in receiver SOAP CC

Hello.
We have increase the support package level of our XI 3.0 system from level 17 to 23. After this "upgrade" all interfaces using a receiver SOAP channel communication are getting the next error:
SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldnt retrieve binding for the given channelId: Binding:CID=8cb6335a548730ea9ca27aaa78034109; at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBindingByChannelId(AbstractLookupManager.java:361) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:421) 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:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
We have done the next steps:
- Run SXI_CACHE and start a complete cache refresh,
- http://<Host>:<portNo.>/CPACache/refresh?mode=full
- Restart J2EE server.
The problem isn't solved.
any idea?

Probably you need to ask your BASIS team if they have done it or not.
Secondly you can just see if something has been done under SWCV SAP BASIS --- http://sap.com/xi/XI/System --- Adapter Metadata, just by oping any adapter and then by looking at Properties or Hisotry from menu "Adapter Metadata". Here you can see the date under "Changed on", so if this matches with your upgrade date then something has been done. But this check will not help you know about the SP level. So better to ask with BASIS.

Error in the Receiver SOAP Adapter

Hello Experts,
I am sending an order number by running a report on the ECC 6.0 server to a web service for publishing the information on the web site. The receiver side is configured as Receiver SOAP Adapter . I am getting the following error in the SXMB_MONI Transaction.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.
Kindly let me know to overcome this problem.
Thanks
Best Regards
S Joshi

Hi Ramesh,
The message Iam getting in MONI is as follows:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.
This is the response for the request that i am sending for order creation. I did checked the fields also it is same and the values of the fields too. they all are correct. Over and above this it was working fine till last week , but suddendly this week I am getting this error.
Regards

Receiver SOAP adapter issue

Hi Experts,
I am getting the below error in the receiver SOAP communication channel. "Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out."
Please help me.
Thanks,
--Naresh

naresh j wrote:
Hi,
>
> 1. I am able to open the webservice from my browser.
> 2. I am able to send the data to webservice through SOAP UI. But getting the error while sending the same data from PI.
>
> What else i can check.? Please advice.
>
> --Naresh
are you able to ping or telnet the host server where the WS is hosted from the PI server?
The issue is that the PI server IP addresses might not be opened in the firewall to connect to the web service.

ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error, in Receiver soap A

Greetings All,
In my scenario i am calling external service of SFDC using receiver soap adapter but i am facing below error in the response.
ADAPTER.HTTP_EXCEPTION, HTTP 500 Internal Server Error
I am creating the soap structure/envelope using Java mapping since need to add additional parameter in soap header.
I am setting the URL in java UDF using parameter TServerLocation.
In comm channel checked "do not use soap envlope" also set the format to text/xml using MessageTransformBean.
The service was working fine when tested in SoapUI tool.
Looking forword for your help and will be appreciated.
Thanks,
Sandip

Hello Sandip, I hope you are doing fine!
I`m not sure if you are using a sync or async scenario...
The behavior that you describe is the expected behavior for SOAP receiver adapter in nosoap mode, asynchronous case.
The explanation that lies behind it is that in nosoap mode the bahavior is just similar to pure HTTP communication. An HTTP 4/5 error received from the target server is treated as HTTP internal error and logged into AFW as an error. The message in an asynchronous scenario without acknowledgements is normally seen as successful on IE side as it is successfully sent to the target system. It can be even successfully consumed by the target webservice, but for amo other reason, the HTTP request from SAP PI to the target system returns HTTP 500 error.
If you ask for system delivery acknowledgements, you should get a non-successful delivery acknowledgement.
In synchrnous scenarios, when a response is expected, the behavior is different.
If this is a sync scenario, there is an official patch released on the service marketplace. SAP Note 1533195 is released.
In addition to deploying the patch, apply the additional configuration steps. As per this note, for the default module
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
you will need to set:
Module Key = soap
Parameter Name = noSOAPMakeSysErrFromResponseFault
Parameter Value = false
If you need to bypass the HTTP errors in the communication with the target system, you need to apply note 1055678.
To apply it, just add for the default module
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean in your receiver
channel, Modules tab the following:
Module Key = soap
Parameter Name = XMBWS.NoSOAPIgnoreStatusCode
Parameter Value = false
If you need any SOAP fault related behavior or any other SOAP related feature, you should setup the channel to run normal SOAP mode, since as already mentioned nosoap mode is used now.
In addition, check note:
856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
section "1. Sender Connection"
Q: I get a server error "500 Internal Servler Error" from the
adapter's servlet. What went wrong?
and get the trace to give you more details of the error.
One more thing, VERY IMPORTANT.
I STRONLGY recommend you to update all XI-PI components to latest patch available in the Service Marketplace. Thery are:
XITOOLS, XIESR, XIAF, XIAFC, MESSAGING, XIGUI. Some of them might not be present depending on the release of you system. e.g: 3.0, 7.0, 7.1
I hope this helps you.
Cheers
Jorge Eidelwein

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

Receiver SOAP - Delivery Exception

Similar Messages

Maybe you are looking for