How To Fix /SCMTMS/MC_CON_CACHE171 - &1 total entries in connection cache

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/MC_CON_CACHE -

• Message number: 171

• Message text: &1 total entries in connection cache

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SCMTMS/MC_CON_CACHE171 - &1 total entries in connection cache ?

  The SAP error message /SCMTMS/MC_CON_CACHE171 typically relates to issues with the connection cache in the SAP Transportation Management System (TM). This message indicates that the connection cache has reached its limit for total entries, which can affect the performance and functionality of the system.
  Cause:
  
  
  Connection Cache Limit Reached: The error occurs when the number of entries in the connection cache exceeds the predefined limit. This can happen due to:
  
  A high volume of transactions or connections being processed.
  Inefficient cache management or configuration.
  Long-running processes that do not release their connections.
  
  
  
  Configuration Issues: The cache settings may not be optimized for the current workload, leading to an overflow of connections.
  
  
  Solution:
  
  
  Increase Cache Size: 
  
  You can increase the size of the connection cache in the SAP system settings. This is typically done in the transaction code RZ10 or RZ11, where you can adjust the parameters related to the connection cache.
  Look for parameters like rdisp/HTTP/max_connections or similar settings that control the maximum number of connections.
  
  
  
  Monitor and Optimize Usage:
  
  Regularly monitor the usage of the connection cache to identify patterns or spikes in usage.
  Optimize the processes that are using the cache to ensure that connections are released promptly after use.
  
  
  
  Clear Cache: 
  
  If the cache is full, you may need to clear it. This can sometimes be done through specific transactions or by restarting the relevant services.
  
  
  
  Review Application Logic: 
  
  Check the application logic to ensure that connections are being managed properly. Ensure that connections are closed after their use to prevent leaks.
  
  
  
  Consult SAP Notes: 
  
  Check the SAP Support Portal for any relevant SAP Notes that may provide additional guidance or patches related to this error.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  RZ10 or RZ11 for adjusting parameters.
  SM21 for checking system logs for related errors.
  SM37 for monitoring job logs that may be related to the issue.
  
  
  
  Performance Monitoring: 
  
  Use transaction ST02 (Buffer Monitor) and ST04 (Database Performance Monitor) to analyze performance and identify bottlenecks.
  
  
  
  SAP Documentation: 
  
  Refer to the official SAP documentation for detailed information on connection management and performance tuning in SAP TM.
  
  
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.