My Oracle Support Banner

JDB Maximum Pool Size Changes From 80 (Its Defined Value) To 4 Post AI Tomcat Restart - Possibly Causing Error "Unable to borrow jdb from pool for User : xxxxx/nTimeout waiting for idle object" (Doc ID 2938545.1)

Last updated on AUGUST 10, 2023

Applies to:

Siebel Finance Service - Version 21.7 and later
Siebel CRM - Version 21.7 and later
Information in this document applies to any platform.


When restarting the AI tomcat and Enterprise as mitigation steps for the bug in (Doc ID 2820807.1), in several situations, the JDB pool size changes from 80 to 4, even though Maximum Possible Connections remains 80 in AI profile.

Below is a snippet of the siebel_1.log showing the change in behavior. Before the restart, the pool size is 80, as in 4/80, after the restart, it is 4, as in 1/4:

The issue can be reproduced at will with the following steps:
1. Perform various restart sequences for AI tomcat and Enterprise in order to mitigate the bug in (Doc ID 2820807.1).
2. Send JDB requests.
3. Notice the change in JDB pool size in the siebel_1.log.


Restart the Tomcat services.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.