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
\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

Similar Messages

What is payload, xi-soap message and xml payload....

can any 1 explains abt What is payload, xi-soap message and xml payload....

Hi Shiva,
see this abstract from messages file:
"The SOAP header of a message contains all the important information that the Integration Server requires to forward the message, while the payload contains the actual business data (such as <PurchaseOrder> in the example above). <b>You can also append an unlimited number of attachments to the message before it is sent. Attachments typically comprise non-XML data, for example, pictures, text documents, or binary data."</b>
Check this link for more info:
http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm
Regards,
Subhasha

USSD message, cannot be read after Amber

920T, the USSD message cannot be read after Amber. It seems the encoding error..
Please advice.

Yes I did, but they said they never saw this problem before, so they have no idea on it..

How to get Payload of SOAP Message in Advance Adapter Engine

HI All,
I am wondering if anybody can tell me how to view the Payload of SOAP Sender and Receiver Message in Advance Adapter Engine?
Does Anybody know how to check mapping payload in Advance Adapter Engine because in ABAP you can see the mapping payload under Request Message Mapping but when you use AAE you can't see the Request Message Mapping Payload.
I have a SOAP to RFC Scenario in which I can't see the SOAP Sender and RFC Receiver Mapping Payload.
When I am sending incorrect data to an RFC I am getting this error which is very strange and new to me.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to split a synchronous message
Any comments would be much appreciated.
Thanks,
Iqbal

HI All,
I have managed to find Michal's Blog which is talking about getting the mapping payload but unfortunately I don't know how to create Adapter Module so I am wondering if somebody can please provide me EAR file so that I will request the Basis guys to deploy the code and hopefully this will solve my query.
Michal's Blog
As you all probably know while using local Advanced Adapter Engine (AAE) processing in SAP PI 7.1 the message is logged only once (during processing by sender adapter). This is great in terms of performance but what if we need to check the mapping output? Is there a way do do it somehow? It turns out that we don't have such an option in standard yet. Is there any alternative then?
It turns out there is - a simplest adapter module there is...
Local AAE works in such a way that from the sender adapter it executes the receiver adapter so in the outbound message to PI processing you can see the adapter info logs of the receiver adapter and this is what we can use. The idea is to add an adapter module to the receiver adapter which will put the content of the message into the audit log of PI message processing. We can do it by writing a few lines of code:
PI/XI: target message logging with local AAE not possible ? not anymore...
*Please upload the file in any free site or <REMOVED BY MODERATOR>
<READ RULES OF ENGAGEMENT>
Thanks,
Edited by: Prateek Raj Srivastava on Jan 6, 2012 9:10 PM

Transform payload to SOAP message using XSLT

Hello,
I'm working with e-invoice for Finland (called Finvoice) and is supposed to send a soap message as a file via file/ftp adapter.
The output from SAP is an INVOIC idoc that is mapped to a given output structure. This works fine.
The soap envelope is created via xslt transformation.
The Envelope is created correctly but I'm struggling with how to add the payload to the message. It needs to look as shown below, (I'm just showing the essential part).
My problem is that I don't know how to add the doctype part via xslt:
<?xml version="1.0" encoding="ISO-8859-15"?>
<!DOCTYPE Finvoice SYSTEM "Finvoice.dtd">
I get validation errors when adding this in the xsl. The content of the payload looks good.
Does anyone know how this can be solved?
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<eb:Manifest eb:id="Manifest" eb:version="2.0">
<eb:Reference eb:id="Finvoice" xlink:href="1017000018">
<eb:schema eb:location="http://www.pankkiyhdistys.fi/verkkolasku/finvoice/finvoice.xsd" eb:version="2.0"/>
</eb:Reference>
</eb:Manifest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="ISO-8859-15"?>
<!DOCTYPE Finvoice SYSTEM "Finvoice.dtd">
<?xml-stylesheet type="text/xsl" href="Finvoice.xsl"?>
<Finvoice Version="1.2">
<SellerPartyDetails>
<SellerPartyIdentifier>SellerPartyIdentifier23456789012345</SellerPartyIdentifier>
<SellerOrganisationName>SellerOrganisationName3456789012345</SellerOrganisationName>
// Best regards Hans

hI,
How to add the the below soap frame thru XSLT mapping.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">
<SOAP-ENV:Header>
<eb:MessageHeader xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" SOAP-ENV:mustUnderstand="1" eb:version="2.0">
<eb:From>
<eb:PartyId>0037123456678</eb:PartyId>
<eb:Role>Sender</eb:Role>
</eb:From>
<eb:From>
<eb:PartyId>NDEAFIHH</eb:PartyId>
<eb:Role>Intermediator</eb:Role>
</eb:From>
<eb:To>
<eb:PartyId>FI2757800750155448</eb:PartyId>
<eb:Role>Receiver</eb:Role>
</eb:To>
<eb:To>
<eb:PartyId>OKOYFIHH</eb:PartyId>
<eb:Role>Intermediator</eb:Role>
</eb:To>
<eb:CPAId>yoursandmycpa</eb:CPAId>
<eb:ConversationId/>
<eb:Service>Routing</eb:Service>
<eb:Action>ProcessInvoice</eb:Action>
<eb:MessageData>
<eb:MessageId>20081228-010142</eb:MessageId>
<eb:Timestamp>2008-12-28T01:01:42+03:00</eb:Timestamp>
<eb:RefToMessageId/>
<eb:RefToMessageId>XS1027.LPTF82/268</eb:RefToMessageId>
</eb:MessageData>
</eb:MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<eb:Manifest eb:id="Manifest" eb:version="2.0">
<eb:Reference eb:id="Finvoice" xlink:href="XS1027.LPTF82/268">
<eb:Schema eb:location=" http://www.finvoice.info/yrityksen_verkkolasku/ladattavat/Tekniset tiedostot/schemat/Finvoice.xsd" eb:version="2.0"/>
</eb:Reference>
</eb:Manifest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="ISO-8859-15"?>
<!DOCTYPE Finvoice SYSTEM "Finvoice.dtd">
<?xml-stylesheet type="text/xsl" href="Finvoice.xsl"?>
Thanks and Regards,
Hymavathi

Viber messages cannot be read once I open the app, they are only visible on my preview screen...

HI,
I have a same question like already posted in December by other person, but without a reaction:
I am getting the message previews on my iPhone but once I open the Viber app to actually read the entire message it is not there.
Pls help me to avoid this, I can't read like every 3rd mesagge I get...
Thank you!

Same thing is happening to me whethere the texts are received on the imessage or other text message apps. The message is showing on the lock screen halfway and when I try to pull it it is not here. This is happening since IOS 7. Is there still a glitch??

Error message: cannot be read to or written from

my ipod can't hold no more than 60 songs. can someone please help me. i try the 5 r's and it still didn't work. i need help please. I think it because i updated to 1.4.1

"you don't seem to get it, my brother ipod works fine and mine doesn;t so my computer can't be outdated because we used the same computer and we used the same itunes, so i want to know why his work and mine doesn't. do u understand"
With all due respect, it's you that doesn't understand. It does not matter a jot that your brother's iPod works fine. Read this from the article that everyone keeps linking to.
"These errors can occur anytime iTunes can't read information from or write information to the iPod."
The error is caused when attempting to write info to your iPod.
Things to try.
All the references in that article.
Downgrading the software (you asked in a previous thread for links to old updaters). When you used an older updater, what happened?
Trying your iPod on another computer. Trying another cable.
Format the iPod in Windows.
First, put the iPod into forced disk mode.
See: How to put the iPod into disk mode.
On your PC, go "my computer" and right click on the iPod, then choose "format". Ensure the settings are at "default" and that "quick format" is not checked. Now select "format". When that's finished, restore the iPod using the updater.
If nothing helps, and you still get that error, then your iPod needs to be checked out.

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"?>

<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

User cannot set read or unread on messages

I have a user that is able to view his inbox and read messages. However, he is unable to set items are read/unread. I thought it was a client issue, but the issue occurs when accessing the mailbox via OWA. This only happens in his inbox.
Any subfolders other folders work perfectly fine. Suggestions?
Thanks in advance.
Exchange 2007
Outlook 2013
OWA error message:
Exception
Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException
Exception message: Cannot set read flags.
Call stack
Microsoft.Exchange.Data.Storage.MessageItem.SetReadFlagsInternal(SetReadFlags flags)
Microsoft.Exchange.Data.Storage.MessageItem.MarkAsRead(Boolean suppressReadReceipt, Boolean deferToSave)
Microsoft.Exchange.Clients.Owa.Basic.ReadMessage.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Inner Exception
Exception type: Microsoft.Mapi.MapiExceptionJetErrorReadVerifyFailure
Exception message: MapiExceptionJetErrorReadVerifyFailure:
Unable to set read flag. (hr=0x80004005, ec=-1018) Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=47] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=572][latency=15] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropSetReadFlag [17] Lid: 17082
ROP Error: 0xFFFFFC06 Lid: 31841 Lid: 21921 StoreEc: 0xFFFFFC06 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 1238 Remote Context Overflow Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F
PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag:
0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 Lid: 13236 StoreEc: 0xFFFFFC06 Lid: 5227 StoreEc: 0xFFFFFC06 Lid: 5233 StoreEc: 0xFFFFFC06 Lid: 1750 ---- Remote Context End ---- Lid: 31418 --- ROP Parse
Done --- Lid: 28622 Lid: 24526 StoreEc: 0xFFFFFC06
Call stack
Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo)
Microsoft.Mapi.MapiMessage.SetReadFlag(SetReadFlags readFlags)
Microsoft.Exchange.Data.Storage.MessageItem.SetReadFlagsInternal(SetReadFlags flags)

Hi,
Does the issue only happen to one specific user?
If it is, please follow Amit’s suggestion to move the mailbox to another database to check whether the issue persists. If it fails, we can rebuild the problematic user mailbox by exporting the mailbox, then creating a new mailbox and importing the mailbox
to have a try.
If it still doesn’t work, please collect some application logs in Event Viewer for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

Routing xml (non-soap) messages in OWSM

Hi all,
Normaly we receive soap message from our business partners. These soap messages are then routed internally (by OWSM) to our services based on content (content based routing).
OWSM is used as a proxy. Partners do not refer to a specific service endpoint but to the owsm as the single virtual endpoint.
Recently a new business partner was added. This partner sends pure xml messages instead of soap messages. These messages are received in OWSM and must also be routed to the right service.
However, it seems that routing these xml messages in OWSM does not work. Can anybody give an acknowledgement of this finding that xml (non-soap) messages cannot be routed in OWSM?
If you have any solutions to this issue I would be glad to hear them.
Many regards,
Ton
Edited by: tvdven on 31-mrt-2010 2:23

Ram--
Everywhere in XI, the acronym "LCR" is synonymous with "SLD", System Landscape Directory. It seems like it may be a term they used early on, or maybe it's the German equivalent. The LCR acronym is sprinkled throughout SAP's underlying code.
In your error message, it's complaining about the Business System entry in the SLD.
My first thought would be that either the source or target business system is not configured in the SLD, or you haven't defined the business system properly in the SOAP adapter configuration. See the "XI20 Adapter Engine" manual for instructions on how to configure the SOAP adapter.
NOTE: You may be able to configure the SLD to make this solution work on your own, but for long-term usage, you're going to want an expert to model your system landscape and configure the SLD properly.
--Dan King
Capgemini

JMS sender adapter : message type null is unknown, payload cannot be read

Hello,
We are building a scenario Weblogic -> PI through a JMS adapter, but we are getting the following error in the adapter :
2009-09-29 12:09:58     Information     New JMS message with JMS message ID ID:P<450046.1254218997063.0> received. The XI message ID for this message is e705a65f-3cf6-472a-3675-b04e9862ce45.
2009-09-29 12:09:58     Warning     JMS message ID:P<450046.1254218997063.0>: message type null is unknown, payload cannot be read and will be empty!
2009-09-29 12:09:58     Warning     JMS message ID:P<450046.1254218997063.0>: Payload empty or cannot be read.
2009-09-29 12:09:58     Information     JMS Message was converted to XI message succesfully.
Despite the fact that the message is not readable, PI creates a message anyway but the payload is empty. It is the same issue as described in this thread :
How to read Java Object message from JMS Queue using JMS Adapter .
But there have been no answer there.
We have read many notes but none are relevant, any ideas ????
Many thanks,
GL

Hallo,
Have you seen this note:
[Note 837501 - J2EE JMSAdapter: Empty payloads, unknown JMS message types|https://service.sap.com/sap/support/notes/837501]?
Seems it can be either message
a) does not contain any payload and/or
or
b) is not of type TextMessage or BytesMessage
/Jakub

PI 7.1 SOAP Adapter - Message Payload for Failed Messages - Where to find

We are exposing a webservice through SAP PI. Occassionaly we have customers calling our webservice and some failure occurs. The error is usually the way that the customer is calling the webservice (missing elements, misnamed tags, bad content in the WS payload..). Generally in these cases we can see the error in communication channel monitoring.
Here is an example:
12/12/11 4:39:07 PM com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-complex-type.2.4.b: The content of element 'SupplierInvoice' is not complete. One of '{"":Invoice}' is expected. at line 1, column 227
12/12/11 4:39:06 PM request received for a channel
I understand the issue, but it would be extremely helpful to have the full SOAP Envelope and Payload of a request when it fails. The communication channel will show a SUCESSFUL message payload with a link to it. But it does not show a failed one.
Where can I find the FAILED payload that accompanies this message? These failures occurs before any mapping or being seen in RTWB Adapter Engine message monitoring... I did some searching around, but did not find anything offhand. I would greatly appreciate any pointers from anyone who has crossed this bridge.

Hi,
When the web service is being called by external application, the first point of contact would be the sender communication channel which converts the SOAP message into XML message and pass to integration engine ( In case of success )
But if the web service call fails due to WSDL validation, Authentication issue, Bad content, invalid content type, you would not see the payload in the sender communication channel or in Adapter engine. You can just see error message in the sender communication channel . I have experienced this many times and i always ask the web service team to provide the SOAP message for validation/investigation purpose.

Unable to read payload from the message object in XI

Hello Guys,
Please help me about my problem in XI version 7.0.im quite new here.
im trying to test my config but error message occured. "Unable to read payload from the message object"
when i checked the comm channel this is the error message :
Error during database connection to the database URL 'jdbc:sqlserver://172.16.40.20:1433;databasename=TRAVEL:SelectMethod=cursor' using the JDBC driver 'com.microsoft.sqlserver.jdbc.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://172.16.40.20:1433;databasename=TRAVEL:SelectMethod=cursor': com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "TRAVEL:SelectMethod=cursor" requested by the login. The login failed.'
when i tried my login in sql it works...but in this message the login is failed..what shall i do..
Please advice.
Thanks in advance
aVaDuDz

Hi
Check with the connection string & Authorization of user you have used.
MSSQL string is
jdbc:microsoft:sqlserver://dbhost:1433;databaseName=example;SelectMethod=Cursor
While doing JDBC its good to refer Note 831162 lot of problems can be resolved.
Thanks
Gaurav

Problem: Applets cannot Create SOAP Message Objects using JAX Pack

Hi all
I want to invoke a simple webservice located at a url.
I wish to send a SOAP Message . The Message is creating using
javax.xml.soap package
Here is the code
public void init(){
try{
MessageFactory MF = MessageFactory.newInstance();
SOAPMessage message = MF.createMessage();
SOAPPart SP = message.getSOAPPart();
SOAPEnvelope SE = SP.getEnvelope();
SOAPHeader SH = SE.getHeader();
SOAPBody SB = SE.getBody();
Name bodyName = SE.createName
("testString","L","http://tempuri.org/");
SOAPBodyElement SBE = SB.addBodyElement(bodyName);
}catch(Exception e){}
When I run the applet in a browser I am getting ExceptionInInitializerError or NullPointer Exception.
The same application works when i run as a standalone application. But not in APPLET.
Can somebody help me in this regard

Im trying to do the same thing !!, i have a servlet that processes SOAP messages, and return SOAP messages back.
Like you i have a implementation running with a stand alone client instead of an applet, which runs fine (there are several .jar files that have to be included in the jre/lib/ext directory, in total about a meg!).
Im now looking to incorporate this client into an applet, but it moans about cannot find classes (the JAXM and SOAP classes).
Have you found a solution to this yet ?? Surely you cannot expect the user to download all the required jar files along with the applet??
With regards to your problem try setting up a button that fires off the SOAP Msg and processes the response, i read on the Sun Java Applet tutorials that some code should stay out of the init method(its a bit vague about WHAT should stay out..), maybe this is an example.
Thanks,
(i dont really expect a response as you posted this ages ago !!, but it would be nice.)

Where is the SOAP Payloads of XI Message in host?

Hi to all,
   I'm trying to find the XML documents(SOAP Payloads of XI Message) in PI host.
Anybody knows which file include this files?
   Look forward your help!
   Thanks!

Jean ,
Same query came early morning ...
Information is stored in the table SXMSPMAST (or SXMSPMAST2 ).
This will help you : /people/alessandro.guarneri/blog/2008/09/15/xipi-message-payload-from-java
Regards ,

Payload of SOAP-Message cannot be read

Similar Messages

Maybe you are looking for