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=8620>. 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=8620 Closed Connection Exception on setAutoCommit ------- Additional Comments From [EMAIL PROTECTED] 2002-04-29 14:24 ------- I think Tomcat's using BasicDataSource, so it looks like you can recreate this problem with more than one configuration. >From your stack trace, it would seem that something's called setAutoCommit on DelegeatingConnection when the underlying connection is already closed. Perhaps we could add a test to see if the underlying connection is closed in setAutoCommit, but I'm not sure the exception in that case is incorrect. I'm guessing that for some reason the underlying Connection is already closed when it is returned to the pool. That would explain why the validations fail also. Can you provide a more complete example of what you are doing? A unit test would be ideal, but just a small example of how the pool and its connections are being used would suffice. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
