SAP Knowledge Base Article - Preview

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

Symptom

  • The processing of tRFC is notably very slow and displays a "Transaction recorded" status in SM58. Concurrently, it is observed that the Max.Conn is not fully utilized for the LUW's RFC destination in SMQS. To illustrate, even when the Max.Conn is set to 10, merely 1 or 2 Act.Conn are in use.
  • t/qRFC Scheduler does not use all available resources.
  • IDoc processing delay.
  • Workflow processing delay.

Capture.PNG

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."


Read more...

Environment

  • Operating System independent
  • Database independent
  • SAP NetWeaver
  • SAP Web Application Server for SAP S/4HANA
  • ABAP Platform 

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

Keywords

RFC processing slow, RFC hang, connections not used, SMQS, available resources, Max.Conn, RFC delay, F110, Data distribution jam, VL02N , 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.