CANNOT_READ_PAYLOAD

Hello all,
My current project scenario is Thirdparty <> XI <> SAP  and when Thirdparty system sends a request to XI , it fails saying "Unable to read the payload from the message object" and also in sxmb_moni there is no any payload.
Provided that this scenario is synchronous and is working fine with "soapUI" software. so when the actual thirparty system sends a request its failing in XI.
Also one more thing is that the thirdparty system connects to XI thr web dispatcher and on web dispatcher the payload cant be seen and we have confirmed that web dispatcher is working fine.
So where is the problem exactly ?

Hi,
Uncheck the option Do not use Soap envelop under Convertion.
Check whether your payload message which you are passing in HTTP Client tool is correct or not, try to copy the payload from Integration Repository while testing your mapping program.
Also check the Integration Engine Configuration runtime parameters,
Open Transaction SXMB_ADM -> Integration Engine Configuration -> Change Specific Configuration
Check the values of below given parameters for runtime category, these values must be maintained:
LOGGING, LOGGING_SYNC, LOGGING_PROPAGATION, TRACE_LEVEL and TRACE_LEVEL_PROPAGATION.
Regards
Aashish Sinha

Similar Messages

  • Error CANNOT_READ_PAYLOAD in SOAP Response

    Hi,
    We are deploying a webservice on SAP PI, when we call the SAP PI webservice directly, everything works normal, and we get a response.
    When we call the SAP PI web service through a different J2EE web service, the fields in response are null(though the SOAP message is received), because PI is not able to get the PAYLOAD in the SOAP request, the following error is obtained in the response.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Every other configuration and the web service settings used are the same, Only the direct call to a WEB SERVICE DEPLOYED IN SAP PI engine is redirected through a WEB SERVICE deployed in J2EE engine to the SAP PI engine, is causing problems.
    Please Help..Urgently.
    Thanks..

    Hi,
    You should read these:
    "MAPPING" CANNOT_READ_PAYLOAD
    CANNOT_READ_PAYLOAD
    CANNOT_READ_PAYLOAD
    MAPPING CANNOT READ PAYLOAD
    Cannot  read payload
    Payload of SOAP-Message cannot be read
    There is a lot more

  • CANNOT_READ_PAYLOAD error in Web Service Response

    Hi experts,
    We are deploying a webservice on SAP PI, when we call the SAP PI webservice directly, everything works normal, and we get a response.
    When we call the SAP PI web service through a different J2EE web service, the fields in response are null(though the SOAP message is received), because PI is not able to get the PAYLOAD in the SOAP request, the following error is obtained in the response.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Every other configuration and the web service settings used are the same, Only the direct call to a WEB SERVICE DEPLOYED IN SAP PI engine is redirected through a WEB SERVICE deployed in J2EE engine to the SAP PI engine, is causing problems.
    Please Help..Urgently.
    Thanks..

    Hi,
    Are both requests (plain PI and WS encapsulated) strictily identical ? If PI can not parse body when intermediate WS is invoked, it might be due to a (slight) change in the WS request (ie namespace, declaration etc) ...
    Chris

  • CANNOT_READ_PAYLOAD in prodcution ?

    Hi Guys,
    I get this error sometimes in our production environment for a sysnchronus interface on the sender call Adapter step and with out even making any changes all the other messages will be successfull.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    We have soap adapter on the sender side and can any body explain this behaviour and how can i prevent these type of errrors.
    Thanks,
    Raj

    Hi Guys,
    I have synchronus scenrio soap - soap axis and some times the service on the target side is not available and in such cases i dont get the response and there is no payload and i see only the error message. If the customer sends again the message it will go through, we are facing these errors in production and i am looking for different options to handle these situations
    1. How to handle the empty payloads in mapping?
    2. Is it possible to restart the synchronus messages with the error status "cancelled with errors".
    any ideas or suggestions would be really appreciated
    Thanks,
    Raj

  • Logical Path of  wsdl

    Hi, I´m developing a Adaptive Web service Model in Webdynpro and i´m facing a problem trying to create a model, I don´t know how can i find the logical destination of the wsdl created on xi scenario, i need to give this path to be able to create the model, any clue?
    Note: I´ve already used the phisycal path and doesn´t work
    Thanks in advance

    Matias I can access through URL from my pc to server and the WSDL is shown, the XI server and SHTTPD are running together in different ports but i got the same exception
    Exception on execution of web service with WSDL URL 'http://ip-address:10080/MI_CODES.wsdl' with operation 'MI_CODES' in interface 'MI_CODES'
    Here is my WSDL i think is ok, nothing is missing..
    If we try to consume the webservice through other GUI like SOAP UI the service is successfully executed but i got an error:
    <code>RecoverableException</code>
      <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD
    WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions name="MI_Codes"
                      targetNamespace="urn:company.com:xi:test"
                      xmlns:p1="urn:company.com:xi:test"
                      xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
      <wsdl:types>
        <xsd:schema targetNamespace="urn:company.com:xi:test"
                    xmlns="urn:company.com:xi:test"
                    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
          <xsd:element name="MT_Resp" type="DT_resp"/>
          <xsd:element name="MT_Codes" type="DT_Codes"/>
          <xsd:complexType name="DT_resp">
            <xsd:sequence>
              <xsd:element name="resp" type="xsd:string">
                <xsd:annotation>
                  <xsd:appinfo source="http://sap.com/xi/TextID">917b85306c7f11dca94c0018de7bac49</xsd:appinfo>
                </xsd:annotation>
              </xsd:element>
            </xsd:sequence>
          </xsd:complexType>
          <xsd:complexType name="DT_Codes">
            <xsd:sequence>
              <xsd:element name="Cve_Ur" type="xsd:string">
                <xsd:annotation>
                  <xsd:appinfo source="http://sap.com/xi/TextID">7b8539c06c7e11dcb1f10018de7bac49</xsd:appinfo>
                </xsd:annotation>
              </xsd:element>
              <xsd:element name="Imp_Clc" type="xsd:string">
                <xsd:annotation>
                  <xsd:appinfo source="http://sap.com/xi/TextID">7b8539c16c7e11dcc3590018de7bac49</xsd:appinfo>
                </xsd:annotation>
              </xsd:element>
              <xsd:element name="Num_Clc" type="xsd:string">
                <xsd:annotation>
                  <xsd:appinfo source="http://sap.com/xi/TextID">7b8539c26c7e11dc83ba0018de7bac49</xsd:appinfo>
                </xsd:annotation>
              </xsd:element>
            </xsd:sequence>
          </xsd:complexType>
        </xsd:schema>
      </wsdl:types>
      <wsdl:message name="MT_Codes">
        <wsdl:part name="MT_Codes" element="p1:MT_Codes"
                   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>
      </wsdl:message>
      <wsdl:message name="MT_Resp">
        <wsdl:part name="MT_Resp" element="p1:MT_Resp"
                   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>
      </wsdl:message>
      <wsdl:portType name="MI_Codes">
        <wsdl:operation name="MI_Codes">
          <wsdl:input message="p1:MT_Codes"/>
          <wsdl:output message="p1:MT_Resp"/>
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="MI_CodesBinding" type="p1:MI_Codes"
                    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
        <soap:binding style="document"
                      transport="http://schemas.xmlsoap.org/soap/http"
                      xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
        <wsdl:operation name="MI_Codes">
          <soap:operation soapAction="http://sap.com/xi/WebService/soap1.1"
                          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
          <wsdl:input>
            <soap:body use="literal"
                       xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
          </wsdl:input>
          <wsdl:output>
            <soap:body use="literal"
                       xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="MI_CodesService">
        <wsdl:port name="MI_CodesPort" binding="p1:MI_CodesBinding"
                   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
          <soap:address location="http://host:50000/XISOAPAdapter/MessageServlet?channel=:BS_WS:CC_WS&version=3.0&Sender.Service=ztest&Interface=ztest%5Eztest"
                        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>
    Thank you Matias for your support

  • There is no payload in Soap request

    Hi Expert,
    I am testing Soap to RFC scenario. I am firing the soap request using Altova xmlspy. I am getting the response as cannot read payload. I checked in the Moni, no payload is coming to xi. but i am sending data through soap request. Below the response wat i am getting
    <?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>RecoverableException</code>
                             <text><![CDATA[
    com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:919)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
         at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:167)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:424)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
              ]]></text>
                        </s:SystemError>
                   </detail>
              </SOAP:Fault>
         </SOAP:Body>
    </SOAP:Envelope>
    Please help me out in this issue
    Thanks,
    Venky

    Hi,
    Check whether your payload message which you are passing in HTTP Client tool is correct or not, try to copy the payload from Integration Repository while testing your mapping program.
    Also check the Integration Engine Configuration runtime parameters,
    Open Transaction SXMB_ADM -> Integration Engine Configuration -> Change Specific Configuration
    Check the values of below given parameters for runtime category, these values must be maintained:
    LOGGING, LOGGING_SYNC, LOGGING_PROPAGATION, TRACE_LEVEL and TRACE_LEVEL_PROPAGATION.
    Look into this thread ... it seems something similar with your problem.
    Payload of SOAP-Message cannot be read Try these solutions.
    Regards
    Aashish Sinha

  • Handling SOAP fault

    Hi,
    we call a web service from Netweaver 7.0 ABAP system through PI.
    So the scenario is Netweaver 7.0 ABAP -> PI -> Web service (HTTP SOAP)
    When the web service gives a SOAP Fault, it returns an error message which we want to be able to get in the ABAP calling system. However , when a SOAP Fault happens the mapping fails and the only exception we get back in the abap system is
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
    How can we actually get the real fault message back to the abap system ... ?
    Thanks.

    Are you using the wsdl generated by XI or you have imported the service provider WSDL?
    If its from XI there is nothing more to do just do the inteface mapping with all the mapping (request , response and fault)
    In case you are using the service provide wsdl.... you have to import it into the external definitions of XI.
    Needs to create the interface and select the proper message for the interfaces and do the mapping and use it in interface mapping.
    Hope its clear

  • Sender SOAP adapter: access Header fields (dont use envelope and nosoap=1)

    Hi,
    I've just been going through various blogs regarding the SOAP adapter and receiving the actual unconverted content being sent to xi. Trying this out I dont get the exptected result.
    What I have done is simply created a web service in XI - added '&nosoap=true' to the url and set the flag in 'Do not use SOAP envelope'.
    After this I send synchronous message via xmlspy and receive error 'XIServer:CANNOT_READ_PAYLOAD'.
    When checking data received in MDT I only see the envelope containing my additional header info (provided in the request) + some XI headers + a body. The body however pretty much only contain a manifest. The actual payload data that I sent in my request a gone (hence the error message).
    When looking i SXMB_MONI i (naturally) also only see the header and body info - no payload. So when mapping step is reached it complains.
    I'm aware I should use mapping like xslt/java to map the message. But first I need to see the payload.
    Anybody got any clues?
    For information I'm running 2004 SP 19.
    Best Regards,
    Daniel

    Hi,
    This is not a matter of logging or trace levels - all these thing a set as needed.
    I do see the messages but I don't see the actual payload (the body-part sent with my request) in neither the AFW or IE.
    Regards,
    Daniel

  • Process 0kb empty file and deliver to target directory

    Hello Experts,
    We had a requirements to process an empty file handling and send it to the receiver/target directory. We had configured to "Process Empty File" Handling and “Write Empty File. The 0KB file polling successfully and archived to the directory with empty payload, but the message output was never created/sent to the target directory. In smxi_moni error message displayed:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Since this is an empty file, there are no mappings involved.  Is there a way to that we could check for 0kb file? If it is empty file, we want to pass/place the empty file to the target directory and if it is not empty, we want the message to process in the standard way.

    Hi David,
    "Since this is an empty file, there are no mappings involved. "
    do you mean you didnt do the mapping at all cos it is empty file ?
    though it is empty file still you need to do the mapping as usually,but when you check the option process the empty file both in sender and receiver adapter ,then it will process even an empty file comes.if you dont check these options and you get an empty file during the process then the mapping will fail.
    in real time you don't know which one is empty file right,but her you know cos you are placing empty file.
    I think you got to do all the steps you do in eneral for a scenario and top on that you have to check process empty file in both sender and receiver adapters,but you may not see the payload in SXMB_MONI.
    but search in SDn you get lot stuff.

  • Payload of SOAP-Message cannot be read

    Hi,
    I'm sending an easy message to the XI 3.0 soap-adapter:
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
         <SOAP:Header/>
         <SOAP:Body>
              <plain>test</plain>
         </SOAP:Body>
    </SOAP:Envelope>
    Unfortunately I get always the error:
    <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
    Thank you for reading und help,  
    Udo

    Hi Stefan,
    Yes, I go from Client to XI to R/3 via SOAP.
    I don't know how the wsdl can solve my problem.
    I use wfetch to send the message. I sent to
    http://host:port/XISOAPAdapter/MessageServlet?channel=
    :service:channel
    as described in sap bibliothek.
    Without the right namespace in the channel the receiver determination runs to an error but it works fine.
    We are on XI 3.0 SP 9.
    The error message coming from XI back to wfetch:
    [code]<?xml version='1.0'?>\r\n
    <!-- see the documentation -->\r\n
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>\r\n
      <SOAP:Body>\r\n
        <SOAP:Fault>\r\n
          <faultcode>SOAP:Server</faultcode>\r\n
          <faultstring>failed to call the adapter engine</faultstring>\r\n
          <detail>\r\n
            <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>\r\n
              <context>XIAdapter</context>\r\n
              <code>DeliveryException</code>\r\n
              <text><![CDATA[\r\n
    com.sap.aii.af.mp.module.ModuleException\r\n
    \tat com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)\r\n
    \tat com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)\r\n
    \tat com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)\r\n
    \tat com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)\r\n
    \tat com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:513)\r\n
    \tat javax.servlet.http.HttpServlet.service(HttpServlet.java:760)\r\n
    \tat javax.servlet.http.HttpServlet.service(HttpServlet.java:853)\r\n
    \tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)\r\n
    \tat com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)\r\n
    \tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:339)\r\n
    \tat com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:317)\r\n
    \tat com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:810)\r\n
    \tat com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)\r\n
    \tat com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)\r\n
    \tat com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)\r\n
    \tat com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)\r\n
    \tat com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)\r\n
    \tat com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)\r\n
    \tat java.security.AccessController.doPrivileged(Native Method)\r\n
    \tat com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)\r\n
    \tat com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)\r\n
    Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception used by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:\r\n
    \tat com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:122)\r\n
    \tat com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)\r\n
    \tat com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)\r\n
    \tat com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)\r\n
    \t... 20 more\r\n
    Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:\r\n
    \tat com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:366)\r\n
    \tat com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:123)\r\n
    \tat com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:419)\r\n
    \tat com.sap.engine.frame.core.thread.Task.run(Task.java:60)\r\n
    \tat com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)\r\n
    \tat com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)\r\n
              ]]></text>\r\n
            </s:SystemError>\r\n
          </detail>\r\n
        </SOAP:Fault>\r\n
      </SOAP:Body>\r\n
    </SOAP:Envelope>\r\n
    [/code]
    Regards (and thanks for your help), Udo

  • HTTP - SOAP

    Hi gurus,
    We want to create the following scenario:
    HTTP - XI - SOAP
    We have test with several combinations of the parameters of the HTTP Adapter Sender and the SOAP Adapter Receiver and we obtain:
    java.io.IOException: invalid content type for SOAP: APPLICATION/OCTET-STREAM
    at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:363)
    at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)
    at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:359)
    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:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    or
    XIServerUNKNOWN.DeliveryException
    com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:
    at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:451)
    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:831)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Also we have proven with several modules and parameters in the SOAP Adapter.
    The HTTP Service is run (sicf) and SOAP too.
    They do not exist mappings, both structures are identical. We test the operation by means of a page HTML with the method post.
    In the HTTP Adapter we have checked “Apply URL Parameters” and added the names of the parameters that we will send in the Post.
    What can be happening?
    Thanks

    I attempt to explain better:
    I use a page .html (POST) in order to invoke a one Web Service.
    HTTP Adapter Sync--> Web Service (SOAP)
    I configure HTTP Adapter Sender:
    <a href="http://es.geocities.com/jsahagung/SDN/HTTPSender.JPG">HTTP Adapter Sender Configuration</a>
    I configure SOAP Adapter Receiver:
    <a href="http://es.geocities.com/jsahagung/SDN/SOAPReceiver.JPG">SOAP Adapter Receiver Configuration</a>
    and
    <a href="http://es.geocities.com/jsahagung/SDN/SOAPReceiver-Module.JPG">SOAP Adapter Receiver Configuration</a>
    The code of HTML:
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <HTML>
    <HEAD>
    <TITLE>Test HTTP Adapter</TITLE>
    </HEAD>
    <BODY>
    <FORM METHOD=POST ACTION="http://host:ABAPPort/sap/xi/adapter_plain?namespace=http%3A//calculadora.es
    &interface=MI_OUT&service=BS_Sender&QOS=BEhttpclient&sap-user=XXXXXXXXXX
    &sap-password=XXXXXXXX&sap-client=XXX">
    OPER1: <INPUT TYPE="text" NAME="OPER1"><BR>
    OPER2: <INPUT TYPE="text" NAME="OPER2"><BR>
    OPERATOR: <INPUT TYPE="text" NAME="OPERATOR"><BR><BR>
    <INPUT TYPE="submit">
    </FORM>
    </BODY>
    </HTML>
    Well, with this configuration, the error that shows is: “CANNOT_READ_PAYLOAD”.
    If I delete module "localejbs/AF_Modules/MessageTransformationBean" and checked "Do not Use SOAP Envelope" the error that shows is: "invalid content type for SOAP: APPLICATION/OCTET-STREAM".
    I don't mapping.
    The content-type of request is application/x-www-form-urlencoded (SXMB_MONI)
    My questions are:
    1 - What is wrong?
    2 - How I must to configurate communication channel so that the scenario works?
    3 - Is Message Mapping with Java mapping necesary?
    4 - Are there any blog with this scenario?
    5 - The HTTP Adapter automatically doesn't transform request HTTP into XML/XI?

  • HTTP to RFC Interface Determination problem

    Hi experts,
    I am doing HTTP <-> RFC scenario mentioned in blog
    /people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
    almost everthing is done; but while configuring the interface determination, i am not able to see the inbound interface.
    your valuable help would be appreciated
    Regards
    Sumit Bhutani

    Hi Bhavesh,
    Thanks for your quick response; this problem has been resolved, but while testing my scenario using RWB i am getting this error.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Please suggest on this
    Thanks
    Sumit

  • XI error Cannot read Pool-Stamp. /Connection is invalid.

    Please assist. These problems seems to be related and are occuring intermitantly on our XI system. Here are the details:
    Connection is invalid.
    Thrown:
    MESSAGE ID: com.sap.aii.utilxi.misc.api.ResourceException
    com.sap.aii.utilxi.misc.api.ResourceException: Connection is invalid.
         at com.sap.aii.utilxi.sql.api.ReusableStatement.get(ReusableStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.ReusableStatement.bind(ReusableStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.bind(AbstractStatement.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.get(AbstractStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.get(AbstractStatement.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.Selector.getBoundStatement(Selector.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.Selector.select(Selector.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.SelectClause.select(SelectClause.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.SelectClause.select(SelectClause.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.StampPersistor.getCurrentStamp(StampPersistor.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.StampPersistor.getCurrentStamp(StampPersistor.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool$MappingStamp.getCurrentStamp(MappingPool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool$MappingStamp.isSameStamp(MappingPool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.pool.SynchronizedGlobalStamp.isSameStamp(Pool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.pool.Pool.checkOut(Pool.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool.checkOut(MappingPool.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java(Compiled Code))
         at sun.reflect.GeneratedMethodAccessor288.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
         at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code))
         at $Proxy184.processFunction(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor77631.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
         at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code))
         at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code))
         at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.run(JCO.java:8043)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged1(Native Method)
         at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
    Serialized server exceptions:
    MESSAGE ID: com.sap.engine.services.dbpool.exceptions.BaseSQLException (serialized)
    com.sap.engine.services.dbpool.exceptions.BaseSQLException: Connection is invalid.
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.checkIfInvalid(ConnectionHandle.java(Inlined Compiled Code))
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.checkIfValid(ConnectionHandle.java(Compiled Code))
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.ReusableStatement.get(ReusableStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.ReusableStatement.bind(ReusableStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.bind(AbstractStatement.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.get(AbstractStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.get(AbstractStatement.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.Selector.getBoundStatement(Selector.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.Selector.select(Selector.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.SelectClause.select(SelectClause.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.SelectClause.select(SelectClause.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.StampPersistor.getCurrentStamp(StampPersistor.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.StampPersistor.getCurrentStamp(StampPersistor.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool$MappingStamp.getCurrentStamp(MappingPool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool$MappingStamp.isSameStamp(MappingPool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.pool.SynchronizedGlobalStamp.isSameStamp(Pool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.pool.Pool.checkOut(Pool.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool.checkOut(MappingPool.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java(Compiled Code))
         at sun.reflect.GeneratedMethodAccessor288.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
         at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code))
         at $Proxy184.processFunction(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor77631.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
         at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code))
         at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code))
         at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.run(JCO.java:8043)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged1(Native Method)
         at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
    Cannot read Pool-Stamp.
    Thrown:
    MESSAGE ID: com.sap.aii.utilxi.misc.api.ResourceException
    com.sap.aii.utilxi.misc.api.ResourceException: Connection is invalid.
         at com.sap.aii.utilxi.sql.api.ReusableStatement.get(ReusableStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.ReusableStatement.bind(ReusableStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.bind(AbstractStatement.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.get(AbstractStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.get(AbstractStatement.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.Selector.getBoundStatement(Selector.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.Selector.select(Selector.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.SelectClause.select(SelectClause.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.SelectClause.select(SelectClause.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.StampPersistor.getCurrentStamp(StampPersistor.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.StampPersistor.getCurrentStamp(StampPersistor.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool$MappingStamp.getCurrentStamp(MappingPool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool$MappingStamp.isSameStamp(MappingPool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.pool.SynchronizedGlobalStamp.isSameStamp(Pool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.pool.Pool.checkOut(Pool.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool.checkOut(MappingPool.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java(Compiled Code))
         at sun.reflect.GeneratedMethodAccessor288.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
         at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code))
         at $Proxy184.processFunction(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor77631.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
         at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code))
         at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code))
         at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.run(JCO.java:8043)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged1(Native Method)
         at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
    Serialized server exceptions:
    MESSAGE ID: com.sap.engine.services.dbpool.exceptions.BaseSQLException (serialized)
    com.sap.engine.services.dbpool.exceptions.BaseSQLException: Connection is invalid.
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.checkIfInvalid(ConnectionHandle.java(Inlined Compiled Code))
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.checkIfValid(ConnectionHandle.java(Compiled Code))
         at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.ReusableStatement.get(ReusableStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.ReusableStatement.bind(ReusableStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.bind(AbstractStatement.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.get(AbstractStatement.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.AbstractStatement.get(AbstractStatement.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.Selector.getBoundStatement(Selector.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.Selector.select(Selector.java(Compiled Code))
         at com.sap.aii.utilxi.sql.api.SelectClause.select(SelectClause.java(Inlined Compiled Code))
         at com.sap.aii.utilxi.sql.api.SelectClause.select(SelectClause.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.StampPersistor.getCurrentStamp(StampPersistor.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.StampPersistor.getCurrentStamp(StampPersistor.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool$MappingStamp.getCurrentStamp(MappingPool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool$MappingStamp.isSameStamp(MappingPool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.pool.SynchronizedGlobalStamp.isSameStamp(Pool.java(Inlined Compiled Code))
         at com.sap.aii.ibrun.server.mapping.pool.Pool.checkOut(Pool.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingPool.checkOut(MappingPool.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.JavaMapping.load(JavaMapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java(Compiled Code))
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java(Compiled Code))
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java(Compiled Code))
         at sun.reflect.GeneratedMethodAccessor288.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
         at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code))
         at $Proxy184.processFunction(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor77631.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
         at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code))
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code))
         at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code))
         at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code))
         at com.sap.mw.jco.JCO$Server.run(JCO.java:8043)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged1(Native Method)
         at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))

    Hi,
    You should read these:
    "MAPPING" CANNOT_READ_PAYLOAD
    CANNOT_READ_PAYLOAD
    CANNOT_READ_PAYLOAD
    MAPPING CANNOT READ PAYLOAD
    Cannot  read payload
    Payload of SOAP-Message cannot be read
    There is a lot more

  • CANNOT_READ_PALOAD error with SOAP to PROXY Synchronous interface

    Hi,
       Problem with SOAP to PROXY Synchronous interface.
    In Production client, some times we are getting the below shown error in SXMB_MONI. There is no Inbound payload also.
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to read payload from the message object</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Please suggest me to resolve this.
    Thanks in advance,
    Hari.

    Hi Hari,
    In your case, check SAP Notes: 1082111 and  1060723.
    Regards,
    P.Rajesh

  • MQ2IDOC problem

    hello experts
    I have an interface MQ2IDOC and reciever this error in the sxmb_moni. the mapping seem the same, and couldnt find the poblem. assistance needed.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to read the payload from the message object</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks
    Kfir

    Hi,
    Check the MQ side if you have a valid messge/data in the MQ Queue.
    Regards,
    Sarvesh

Maybe you are looking for

  • HT4528 I cannot SEND email from my iPhone 5S. I can receive emails, but not send them

    I cannot SEND emails from my iPhone 5S

  • Voice memos app

    I will try not to sound too confusing.  I have HUNDREDS of recordings in Voice Memo app of my iPhone 4 (IOS 6.1.3).  (I am a writer and write alot this way, though have of late switched to other voice apps with more flexibility).  My goal is to get t

  • Flickering my new imac 2013

    I have my imac 27inch 2013  for 14 days and suddenly display started flickering when I scroll down the pages or open some applications.Please help me .

  • Sync Help! Competing Libraries!

    I no longer have the original computer I began syncing my iPhone and iPad on, and have moved to my girlfriend's laptop. She has a full library; where I can log her out of iTunes, but her library stays. How do I sync to get updates and sync my iPad wi

  • How can we add Text field on system form which is updateable?

    Hi Experts I Want to create text field on System Form like A/R Invoice, in which I can store value after saving the document. I means Updateable field. Is it possible and How? Thanks Regards Gorge