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 16987] - race condition in PoolableConnection.close()
Date Tue, 15 Apr 2003 17:07:06 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=16987>.
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=16987

race condition in PoolableConnection.close()





------- Additional Comments From mohankishore@yahoo.com  2003-04-15 17:07 -------
Had submitted a patch which included making the close() method no-op when 
called twice. Noticed that the test harness had a method called 
CantCloseConnectionTwice - changed it to CanCloseConnectionTwice. Had to make 
the CPDS ConnectionImpl's close() method conform to the no-op too.

Admit that its slightly highjacking the original report. Maybe should open a 
separate bug for these. btw, the problem also exists for Statement.close() 
method - i.e. it should also be a no-op for a closed statement. Didnt find it 
categorically stated for the ResultSet though...

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