Cannot Allocate A Connection From The GlassFish Server JDBC Connection Pool Due To In-use Connections Equal max-pool-size
(Doc ID 1473945.1)
Last updated on APRIL 05, 2018
Applies to:Oracle GlassFish Server - Version 2.1.1 to 3.1.2 [Release 2.1 to 3.1]
Information in this document applies to any platform.
***Checked for relevance on 13-Jun-2014***
The application server log contains errors similar to the following, though the error stacks will be application/customer specific and they have been truncated for clarity:
In the above error stack the highlighted lines indicate where in the application's code the connection is being allocated from. The top of the stack is not relevant as that simply shows the steps in the application server needed to find and return a connection to the application. Therefore, in this example, the application/customer specific code in the com.acme.jdbc.common.DBManager.establishConnection() and com.acme.jdbc.common.DBManager.deleteOldDetails() methods would need to be investigated to determine if there is any problems with the JDBC resource handling.
If no "potential connection leak" messages are seen then the likelihood is you have insufficient capacity configured for your workload.
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