cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC message processing failed; reason Unknown payload format 0 in message

pedro_baroni3
Active Contributor
0 Kudos

Hi Experts,

In Asynchronous Interface (Proxy -> JDBC), occured an error in Adapter Engine, but the payload is OK in the SXI_MONITOR.

Payload in SXMB_MONI:


<?xml version="1.0" encoding="UTF-8" ?> 
<ns0:MTP_XPTO xmlns:ns0="http://xpto">
   <Statment>
      <xpto action="INSERT">
         <table>TABLE_NAME</table> 
         <access>
            <ID_PRO>000000000000000001</ID_PRO> 
            <ID_EST>XX</ID_EST> 
            <CD_SITUACAO>1</CD_SITUACAO> 
            <ID_CTF>00</ID_CTF> 
            <NR_CLF>9019.10.00</NR_CLF> 
            <ID_ORI>00</ID_ORI> 
            <PC_ICMS>0.00</PC_ICMS> 
            <PC_ICMS_SUBST_SAI>0.00</PC_ICMS_SUBST_SAI> 
            <PC_ICMS_REDUZ_SAI>0.00</PC_ICMS_REDUZ_SAI> 
            <PC_ICMS_DIF_SAI>0.00</PC_ICMS_DIF_SAI> 
            <PC_IPI>0.00</PC_IPI> 
            <CD_PIS>0.00</CD_PIS> 
            <CD_CONTR_SOCIAL>0.00</CD_CONTR_SOCIAL> 
            <CD_ISS>0.00</CD_ISS> 
            <PC_ICMS_REDUZ_ENT>0.00</PC_ICMS_REDUZ_ENT> 
         </access>
      </xpto>
   </Statment>
</ns0:MTP_XPTO>

Message Display Tool (Detail Display): Audit Log


15.08.2011 01:52:57 Error JDBC message processing failed; reason Unknown payload format 0 in message 
15.08.2011 01:52:57 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Unknown payload format 0 in message 
15.08.2011 01:52:57 Error Exception caught by adapter framework: Unknown payload format 0 in message 
15.08.2011 01:52:57 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Unknown payload format 0 in message. 

Message Display Tool (Detail Display): Message Content


content-length:237563
accept-encoding:gzip
sap-xi-messageid:FDC3484EBA6F5F0CE10000000A0000B1
http:POST
host:qqmtz645:50000
user-agent:SAP Web Application Server (1.0;700)
content-type:multipart/related;boundary=SAP_248A484E4087AB5EE10000000A0000C1_END;type="text/xml";start="<soap-238A484E4087AB5EE10000000A0000C1#sap.com>"
soapaction:"http://sap.com/xi/XI/Message/30"

Error in J2EE Cluster Log:


#1.5 #001E0B5D3AC8006D000013DC000060B60004AA84096C7B97#1313383977352#/Applications
/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#sap.com
/com.sap.aii.af.app#com.sap.aii.adapter.jdbc.XI2JDBC.processMessage(Message)#J2EE_GUEST#0#SAP J2EE Engine JTA 
Transaction : [04e173800ffffffe8ffffff8d]#n/a##7bd7618ac68f11e09c020000004e1738#XI 
XI2JDBC[CHN_JDBC_XPTO_RCV_PRD/BS_XPTO
/]_24544##0#0#Error#1#com.sap.aii.adapter.jdbc.XI2JDBC#Plain###JDBC processing failed: Unknown payload format 0 in 
message#

#1.5 #001E0B5D3AC8006D000013DE000060B60004AA84096CE00B#1313383977377#/Applications
/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#sap.com
/com.sap.aii.af.app#com.sap.aii.adapter.jdbc.XI2JDBC.addAuditLog(AuditMessageKey, AuditLogStatus, String, 
String,Object[])#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : 
[04e173800ffffffe8ffffff8d]#n/a##7bd7618ac68f11e09c020000004e1738#XI 
XI2JDBC[CHN_JDBC_XPTO_RCV_PRD/BS_XPTO
/]_24544##0#0#Error#1#com.sap.aii.adapter.jdbc.XI2JDBC#Plain###JDBC_ERR_602#

Any idea about this?

Tks in advance.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello,

You could also check note

#1112675 XI messages may not be read correctly from database in AF

Regards

Sarah

pedro_baroni3
Active Contributor
0 Kudos

Hi Sarah,

I checked the patch for this note and my environment is updated (SP23).

I try "Reset Content Length" and checked the contents of the message through "Export". The payload is present and correct, but it is not possible to reprocess, the error remains.

Any ideas?

Thanks in advance.

Former Member
0 Kudos

Hi Pedro,

I see that you are on a higher patch than mentioned in the note.

Did you try going to the url in the note:

http://host:port/MessagingSystem/monitor/dbconsistency.jsp

Kind regards,

Sarah

pedro_baroni3
Active Contributor
0 Kudos

Hi Sarah,

Yes, in URL http://host:port/MessagingSystem/monitor/dbconsistency.jsp, I try "Reset Content Length" and checked the contents of the message through "Export". The payload is present and correct, but it is not Possible to reprocess, the error remains.

Tks.

pedro_baroni3
Active Contributor
0 Kudos

Hi Experts,

Any idea?

Tks in advance.

pedro_baroni3
Active Contributor
0 Kudos

Hello Experts!

This problem does not happen again. Happened when accumulated many messages with the TBDL Status due to the slowness of some JDBC Interfaces Receiver. Improvements were developed in the table indexes in the Legacy Database.

Tks.

Answers (1)

Answers (1)

Former Member
0 Kudos

pedro_baroni3
Active Contributor
0 Kudos

Hi Amit,

I see this link but this solution did not answer.

This error occurs sporadically in this interface, most of the time (99%) it does not occur.

Tks.

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Just curious the tag Statement has typo... Also are you sending the expected jdbc structure, Please check ? see whether that helps..

One more findings in your structure...

First table tag then followed by tablename tag with action something as below

<Statement>
<table>realDbTableName</table>

<dbTableName action=u201DINSERTu201D>

<access>

<col1>val1</col1>

<col2>val2</col2>

</access>

</dbTableName>
</Statement>

.

Edited by: Baskar Gopal on Aug 15, 2011 2:43 PM

pedro_baroni3
Active Contributor
0 Kudos

Hi Baskar,

This structure is functioning normally, because 99% of the messages for this interface works correctly.

Tks.