"MAPPING" CANNOT_READ_PAYLOAD

Former Member · ‎10-15-2009

Hi,

Our scenario is the following:

R/3 -> XI 3.0 -> PeopleSoft

RFC HTTP

The interface is syncronous.

First of all this interface works perfectly in the developpment system and in other systems (dev-cons-prod) we have a similar functionnality and it works well. Only in this consolidation system it works from time to time: the third time it doesn´t work anymore.

In the Integration Engine we´ve activated the following parameters to see more but it didn´t help much:

RUNTIME LOGGING 1

RUNTIME LOGGING_PROPAGATION 1

RUNTIME LOGGING_SYNC 1

RUNTIME TRACE_LEVEL 3

RUNTIME TRACE_LEVEL_PROPAGATION 1

Those 3 messages appear as follows (i´ve deleted confidential information) in SXI_MONITOR:

SENDER: RECEIVER:

1- IR1CLNT200 PSCorp CENTRAL AENGINE @5F@ sincrónico 200

2- Error - Restart Not Possible

PSCorp IR1CLNT200 CENTRAL PLAINHTTP AENGINE @5F@ sinc 200

3- Error - Restart Not Possible@

PSCorp IR1CLNT200 CENTRAL AENGINE PLAINHTTP @5F@ sinc 200

Details of the third erroneous message:

<?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 the payload from the message object</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

In the sender system we have the following dump when we try the function module from transaction SE37:

Runtime Errors CALL_FUNCTION_REMOTE_ERROR

Date and Time 15.10.2009 16:30:21

ShrtText

"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:

We´ve activated also in the Visual Administrator the log ("debug" level) in the "Log Configurator" and all that we can see at OS level is the following trace:

#1.5#00145E47B2F4004F0000005F00069032000475F9E84854AF#1255616111203#com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean#sap.com/com.sap.aii.adapter.rfc.app#com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(ModuleContext moduleContext, ModuleData inputModuleData)#J2EE_GUEST#0####257bf580b99511deb5fe00145e47b2f4#output##0#0#Warning##Java###Catching #1#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:127) at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:832) at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56) 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) # #1.5#00145E47B2F4004F0000006000069032000475F9E84855A6#1255616111203#com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean#sap.com/com.sap.aii.adapter.rfc.app#com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(ModuleContext moduleContext, ModuleData inputModuleData)#J2EE_GUEST#0####257bf580b99511deb5fe00145e47b2f4#output##0#0#Path##Java###Throwing #1#com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD: caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:#

#1.5#00145E47B2F4004F0000006100069032000475F9E8485663#1255616111203#com.sap.aii.af.mp.ejb.ModuleProcessorBean#sap.com/com.sap.aii.af.app#com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)#J2EE_GUEST#0####257bf580b99511deb5fe00145e47b2f4#output##0#0#Error##Plain###Error during processing local bean localejbs/RfcAFBean#

#1.5#00145E47B2F4004F0000006200069032000475F9E8485834#1255616111204#com.sap.aii.af.rfc.afcommunication.to.impl.AbstractToAF##com.sap.aii.af.rfc.afcommunication.to.impl.AbstractToAF.consumeAfterProduce(Object[] request)#J2EE_GUEST#0####257bf580b99511deb5fe00145e47b2f4#output##0#0#Warning##Java###Catching #1#com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD: caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:

at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:308)

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

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

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

at com.sap.aii.af.rfc.afcommunication.to.impl.AbstractToAF.consumeAfterProduce(AbstractToAF.java:313)

at com.sap.aii.af.service.util.concurrent.AbstractProducerConsumer.consume(AbstractProducerConsumer.java:370)

at com.sap.aii.af.rfc.afcommunication.to.impl.ToAFDynamic.run(ToAFDynamic.java:132)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

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

Caused by: 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:127)

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

at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)

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)

What´s happening? Why does this interface work only sometime?

Thanks in advance

Former Member · ‎11-04-2009

Hi,

The issue has been solved.

The problem was a firewall issue. One Application Server couldn´t reach the receiver.

Thanks

Former Member · ‎10-15-2009