https://issues.apache.org/bugzilla/show_bug.cgi?id=56790
Bug ID: 56790
Summary: Resizing pool.maxActive to a higher value at runtime
leads to unmanaged connections
Product: Tomcat Modules
Version: unspecified
Hardware: PC
OS: Mac OS X 10.4
Status: NEW
Severity: normal
Priority: P2
Component: jdbc-pool
Assignee: [email protected]
Reporter: [email protected]
Resizing maxActive to a higher value on a live pool leads to
untraceable/unmanaged connections.
The pool accepts the new higher value and accepts to deliver new connections
but the following warning message is logged:
"Connection doesn't fit into busy array, connection will not be traceable."
When looking at the code it appears the ArrayBlockingQueue holding the busy
connections is not resized and keeps its original size: the extra connections
cannot be added to it.
The main consequence is the pool size isn't actually increased. Connections
created past the original maxActive limit will never be pooled but immediately
dropped once closed by the application.
I made a small unit test to illustrate the case - should I post it somewhere?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
