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 Mon, 09 Apr 2007 07:42:32 GMT


Phil Steitz commented on DBCP-212:

After running against instrumented dbcp and pool jars and different db engines, I still can't
replicate this problem.  Both client and server logs are showing only the expected number
of opens and closes on physical connections. I suspect that the connections must either being
closed on the server side or somehow JConnect's isClosed impl is returning true when the connection
is not closed (though it is working for me against SQL Anywhere).  One more thing to try is

> 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, Commons Pool 1.3
>            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