How To Fix ITS_P027 - New session was refused due to memory bottleneck

ITS_P027 - Overview

• Message type: E = Error

• Message class: ITS_P - Web Gui Plug-In

• Message number: 027

• Message text: New session was refused due to memory bottleneck

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 ITS_P027 - New session was refused due to memory bottleneck ?

  The SAP error message "ITS_P027 New session was refused due to memory bottleneck" typically indicates that the Internet Transaction Server (ITS) is unable to allocate sufficient memory to create a new session. This can occur due to various reasons, including high server load, insufficient memory allocation, or configuration issues.
  Causes:
  
  High Load: The server may be experiencing a high number of concurrent sessions, leading to memory exhaustion.
  Insufficient Memory: The server may not have enough physical or virtual memory allocated to handle the current load.
  
  Configuration Issues: The ITS configuration may not be optimized for the current usage patterns, leading to inefficient memory usage.
  Memory Leaks: There could be memory leaks in the application or the server, causing memory to be consumed without being released.
  Resource Limits: Operating system-level resource limits (like ulimit in Unix/Linux) may restrict the amount of memory that can be allocated.
  
  Solutions:
  
  Monitor Server Load: Use monitoring tools to check the current load on