commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Commented: (DBCP-212) PoolingDataSource closes physical connections
Date Fri, 06 Apr 2007 09:29:32 GMT


Phil Steitz commented on DBCP-212:

Can you please provide a little more information on what exactly you are seeing - how exactly
you can tell that the connections are being physically closed? 

I ran the DBCPTester code against postgres and Sybase SQL Anywhere (developer edition, with
the JConnect driver above) and did not see connection leakage or churn.   In each case, I
examined connection logs and there did not appear to be connect-disconnects happening.  Postgres
did not churn processes and the logs showed just 15 connects,  and disconnects only when the
program was terminated.  Same for Sybase.  With Sybase, I did notice a lot of executions of
sp_dba.  This is because the pool periodically  checks isClosed().  The JConnect docs  (
explain why this triggers sp_dba.  Specifying IS_CLOSED_TEST=INTERNAL eliminates this.  

Are you running Commons Pool 1.3?  With dbcp 1.2.2, you should be.  Could you pls also test
using pool 1.2 with dbcp 1.2.1?  I don't see any difference in my tests using the previous
versions and the changes from pool 1.2 / dbcp 1.2.1 to pool 1.3 / dbcp 1.2.2 should not affect
this; but it would be good to know if the behavior you are seeing is new.


> PoolingDataSource closes physical connections
> ---------------------------------------------
>                 Key: DBCP-212
>                 URL:
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>         Environment: Windows XP, Java 1.5.0_06-b05, Sybase ASE 12.5.4, jConnect 6.0.5
EBF 13862
>            Reporter: Marcos Sanz
>         Attachments:
> By executing the attached program and monitoring the process id of the physical connections
at the database server, it is possible to demonstrate that the connections are being actually
physically closed and reopened by the application at a very high rate.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message