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=13235>. 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=13235 referenced UserPassKey instances get erroneously returned to the pool and subsequently reinitialized [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-11-16 19:49 ------- I could not reproduce the problem either, but the use of immutable keys is a better approach and so I have re-implemented as such. Your assumption on the reason for the static map of pools is correct. It is needed in the event multiple instances referring to the same pool of connections are created by the jndi service. Craig has noted that it is correct behavior for the object factory to return a new instance for each lookup. But perhaps it would be clearer to move the logic in the ObjectFactory implementation and maintain instance fields for the pools in the datasource implementation. I still wonder about jndi service providers which use serialization. The mutable key problem is solved though. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
