Oracle WebLogic Server Freezes Due to Connection Pool Saturation: How to Fix It

The root of the problem

When Oracle WebLogic Server experiences freezes or timeout errors (Connection Pool Timeout), the issue is usually related to database connection pool saturation. This mainly happens for two reasons:

• Connections opened by the application are not properly closed in the code, causing resource leaks. Learn more.
• The maximum connection limit configured in the WebLogic console is insufficient to handle the current user load. See details.

How to monitor Data Source status in real time

1. Log in to the WebLogic Administration Console.
2. Navigate to Services > Data Sources.
3. Select the Data Source you want to inspect.
4. On the Monitoring tab, review metrics such as 'Active Connections', 'Waiting For Connection' and 'Highest Num Waiters'. Full guide.

Adjusting the maximum connection pool size

1. Access the WebLogic Administration Console.
2. Select the desired Data Source and click Configuration > Connection Pool.
3. Modify the Maximum Capacity field to increase the maximum number of allowed connections.
4. Click Save to apply the changes. Detailed instructions.

Configuring timeout values to release orphaned resources

1. In the Administration Console, select the corresponding Data Source.
2. Go to Configuration > Connection Pool.
3. Set an appropriate value for Inactive Connection Timeout (for example, 300 seconds).
4. Save the changes to activate the new configuration. More details.

Frequently Asked Questions (FAQs)

What is Connection Pool Timeout in WebLogic?

It is the amount of time a request waits to obtain a connection from the pool before failing. This error occurs when the pool is saturated or no connections are available.

How can I identify connection leaks in WebLogic?

Monitor the Data Source metrics in the administration console and use diagnostic tools such as WebLogic logs or external tools to identify connections that are not being closed.

What values are recommended for Inactive Connection Timeout?

Common values range between 300 and 600 seconds, depending on the application's usage and user load. Adjust this parameter according to the specific needs of your environment.