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 18905] - Couldn't get connection (Jdbc2PoolDataSource)
Date Tue, 10 Jun 2003 07:31:12 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=18905>.
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=18905

Couldn't get connection (Jdbc2PoolDataSource)





------- Additional Comments From tagunov@motor.ru  2003-06-10 07:31 -------
I imagine we could configure f.e. MySQL to accept _any_ password for a given user, or am I

wrong?

Yes, II make things _so_ much easier!

Well, I did not look into the code deep 
enough, maybe it is really necessary to have this master map and ids, but then there's apparently
a 
problem with synchronization: first registXXX synchronizes on this but it should synchronize

on this.getClass() I guess, to be proper. Then all the fetch operations from this common HashMap

must be synchronized. Or some *Bucket*HashMap from collections should be used that is fast
yet 
thread safe.

And, is it possible to obtain a new id via

final int newId;
synchronized( 
this.getClass() )
{
     newId = _staticCounter++;
}

instead of examining the existing 
set of instances?

---------------------------------------------------------------------
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