SAP Knowledge Base Article - Preview

1887368 - tRFC process slow in SM58 and Max.Conn is not fully used in SMQS


  • tRFC processing is very slow and has "Transaction recorded" status in SM58, in the meanwhile, you find the Max.Conn is not fully used for the LUW's RFC destination in SMQS. For example, you define the Max.Conn to 10, but there is only 1 or 2 Act.Conn.
  • IDOC processing delay.
  • Workflow processing delay.




 SAP Release Independent


RFC processing slow, RFC hang, connections not used, SMQS , KBA , BC-MID-RFC-QT , Queued RFC (qRFC) and transactional RFC (tRFC) , Problem

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.