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/04/02 12:29:26 UTC
DO NOT REPLY [Bug 10249] -
Tomcat hangs with Interclient JDBC driver
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=10249>.
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=10249
Tomcat hangs with Interclient JDBC driver
o.rode@deutschepost.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
------- Additional Comments From o.rode@deutschepost.de 2003-04-02 10:29 -------
I had the same bug with Oracle DB. It's very unlikely that this driver hangs.
The problem is caused in the "endless" loop at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject().
After creating the new connection, some check is done:
if(_testOnBorrow && !_factory.validateObject(pair.value)) {
In my configuration the ValidationQuery parameter was generated by the manager
but i left it empty. This caused validateObject() to return false, which then
caused the endless loop. I would expect an Error or any appropriate handling
in this case since it is a fatal misconfiguration.
Workaround: Remove the parameter for the validation query from the config in
server.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org