DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39052>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39052 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Keywords| |FixedInTrunk OS/Version|other |All Platform|Other |All Resolution| |DUPLICATE Version|unspecified |1.2 Final ------- Additional Comments From [EMAIL PROTECTED] 2006-03-22 17:21 ------- There are two ways to view this problem. The first is as a synchronization problem. Pool 1.3 will fix this NPE as a side effect of other synchronization fixes that went in. 1.3 will be released soon and you find a release candidate from: http://people.apache.org/~sandymac/pool/1.3-rc1/ . From this point of view this is really a dupe of Bug #37227 If you could test 1.3-rc1 and confirm that it doesn't have this problem I'd really appreciate it. Unfortunately this fix may still cause IllegalStateExceptions to be thrown by returnObject after the pool has been closed. Pool 2.0 changes the behavior so that when objects are returned to a closed pool the pool should accept those objects and destroy them without errors. Pool 2.0 includes a number of improvements deemed too intrusive for a long over due dot-release. I'm marking this as a dupe of bug #37227. If you disagree or the 1.3-rc1 demonstrates the same problem please reopen this issue. *** This bug has been marked as a duplicate of 37227 *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
