SAP Knowledge Base Article - Preview

3769425 - Large Message Handling Explained in SAP PI/PO Messaging System

Symptom

One or more of the following situations occur in SAP Process Integration / Process Orchestration:

  • Large payload messages cause high Java heap consumption.
  • Message processing is delayed when multiple large messages are processed simultaneously.
  • Messages remain in status To Be Delivered (TBD) or are not scheduled immediately.
  • Large messages are blacklisted and moved to error status.
  • Synchronous requests or responses are unexpectedly blocked after enabling large message handling.
  • Need clarity on how below properties affect processing:
    • messaging.largemessage.enabled
    • messaging.largemessage.threshold
    • messaging.largemessage.permits
    • messaging.largemessage.queueTypes
    • messaging.largemessage.blacklistXLMessage


Read more...

Environment

  • SAP NetWeaver
  • SAP Process Integration 
  • SAP Process Orchestration

Product

SAP NetWeaver all versions

Keywords

pi/po, as java, outofmemoryerror, oom, message size, heap dump, oom.hprof, large message handling, payload, adapter engine, messaging.largemessage.threshold, messaging.largemessage.permits , KBA , BC-XI-CON-MSG , Messaging System , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.