SAP Knowledge Base Article - Preview

1869191 - Backlog when sending Idocs in the foreground using outbound qRFC through a registered RFC destination


During times of peak load you notice the following:

  • In the ALE layer outbound Idocs are delayed in status 30 (delays transferring the outbound Idoc from the ALE layer to the RFC layer). For example you see something like:


  • When these Idocs are finally passed to the RFC layer (status 03) there are again delays transferring them onto their final RFC destination.
  • You notice that the max. connection setting for the used outbound RFC destination in SMQS is not being fully utilized  - for example you have registered the destination with a max. connection setting of 5 but you only ever see 2 active connections for this destination in SMQS (despite the fact that there is a backlog of requests for this destination waiting to be processed).



SAP Release Independent


SAP NetWeaver all versions


KBA , BC-MID-ALE , Integration Technology ALE , BC-MID-RFC , RFC , BC-CST-GW , Gateway/CPIC , 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.