commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18921] - Per User methods not working in Jdbc2PoolDataSource
Date Mon, 14 Apr 2003 19:14:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18921>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18921

Per User methods not working in Jdbc2PoolDataSource





------- Additional Comments From mohankishore@yahoo.com  2003-04-14 19:14 -------
The maxXXX are configuration elements and not meant to be used as a monitoring 
device. The perUserMaxActive defines which pool the user gets a connection 
from. The logic for the numXXX is as follows:

e.g. you can set a perUserMaxActive for user1. Then you open 3 connections, 1 
each for user1, user2, user3. Then, you will get the following results:
getNumActive()            => 2 // user2,user3 in default pool
                               // consistent with JavaDoc...

getNumActive('user1','')  => 1 // user1 has its own pool
getNumActive('user2','')  => 2 // as both user2,user3 in default pool
getNumActive('user3','')  => 2 // as above.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message