You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/03/01 00:04:19 UTC

DO NOT REPLY [Bug 17504] - JDBCRealm start() opens but does not close connection.

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=17504>.
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=17504

JDBCRealm start() opens but does not close connection.

matt@clickability.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From matt@clickability.com  2003-02-28 23:04 -------
Yes, I understand why it is not a problem in the default implementation, but it
is a problem if you are extending this class, in my case, to use a connection pool. 
To prevent the connection from never being closed or returned to the pool, I
have to do some ugly workarounds in the extended class. It seems to me like just
closing the connection opened by start() would be an extremely simple change and
would have little risk of destabilizing anything.

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