DO NOT REPLY [Bug 16581] - Deadlock in AbandonedObjectPool when firewall closes connections

[bugzilla]

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

Deadlock in AbandonedObjectPool when firewall closes connections

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|http://www.newedgenet.com/  |
           Keywords|                            |PatchAvailable
            Summary|Deadlock in                 |Deadlock in
                   |AbandonedObjectPool         |AbandonedObjectPool when
                   |                            |firewall closes connections



------- Additional Comments From [EMAIL PROTECTED]  2003-02-01 01:10 -------
The patch I've contributed works with DBCP 1.0 (the version which is bundled
with Tomcat 4.1.18).  It merely enables properties available in the
GenericObjectPool so that timed pool evictions can close the connections before
the firewall automatically does so.  The patch fits nicely with the property
copying thats already being done from BasicDataSourceFactory to BasicDataSource
to GenericPoolObject.

The following section of XML can now be added to the factory configuration in
server.xml:
                  <parameter>
                    <name>testOnBorrow</name>
                    <value>false</value>
                  </parameter>
                  <parameter>
                    <name>testOnReturn</name>
                    <value>false</value>
                  </parameter>
                  <parameter>
                    <name>timeBetweenEvictionRunsMillis</name>
                    <value>300000</value>
                  </parameter>
                  <parameter>
                    <name>numTestsPerEvictionRun</name>
                    <value>5</value>
                  </parameter>
                  <parameter>
                    <name>minEvictableIdleTimeMillis</name>
                    <value>300000</value>
                  </parameter>
                  <parameter>
                    <name>testWhileIdle</name>
                    <value>true</value>
                  </parameter>

BTW, prior to writing the patch I had tested this application in production with
maxIdle=1 and it has not crashed (since the app is never idle for longer than
the firewalls connection timeout).

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]