You have configured a scenario to exchange messages using a specific adapter (File, Soap, Rfc, Jms, etc.…), but you find out that you have messages stuck in the Adapter Engine side with status “To be delivered”.
- PI Release Independent
- SAP NetWeaver
- SAP Process Integration
Process Integration 7.0, PI 7.0, PI 7.01, PI 7.02, Process Integration 7.10, PI 7.10, Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.40, PI 7.40, PO 7.40, Process Orchestration 7.50, PI 7.50, PO 7.50, NetWeaver, MaxThreadCount, maxConsumers, Adapter Engine, To be delivered, TBDL, Hanging, Struck, Messages, Threads, delivering, tobedelivered, AAE, AE, Runtime Workbench, RWB, PIMON, PI monitor, Message Monitor, Message Monitoring, cannot process, queued, maximum number of threads, file, idoc, soap, rfc, jdbc, ftp, jms, stop, scheduled , KBA , BC-XI-CON-MSG , Messaging System , Problem
About this pageThis 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.