All work

 

Pool exhausted at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject

Fixed

Description

lucee.runtime.exp.NativeException: Pool exhausted
at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:451)
at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:356)
at lucee.runtime.config.DatasourceConnPool.borrowObject(DatasourceConnPool.java:36)
at lucee.runtime.db.DatasourceManagerImpl.getConnection(DatasourceManagerImpl.java:79)
at lucee.runtime.tag.Query.executeDatasoure(Query.java:1120)
at lucee.runtime.tag.Query._doEndTag(Query.java:702)
at lucee.runtime.tag.Query.doEndTag(Query.java:567)

Environment

None

Details

Assignee

Reporter

Priority

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 12 December 2022 at 10:38
Updated 29 April 2025 at 21:24
Resolved 9 January 2023 at 15:11

Activity

Michael Offner 
17 February 2023 at 14:38

issue was that the test case does look at all threads in “cfthread“ instead of the threads in the name list

Michael Offner 
9 January 2023 at 16:35

looking deeper to this, i think this is unrelated to the db pool at all.

Michael Offner 
9 January 2023 at 16:25

seem to be 2 test cases conflicting in that case, in the stacktrace the interupt is in “LDEV3719“, but we are in ticket LDEV4320

Zac Spitzer 
29 December 2022 at 08:53

It’s throwing the following error on Github actions, I have disabled the test for now

Pothys - MitrahSoft 
13 December 2022 at 14:50

I checked this ticket and confirmed the issue happened on the lucee version 6.0.0.313-SNAPSHOT and JMeter. When accessing the datasource concurrently with JMeter, it throws an error like "pool exhausted".