commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DBCP-212) PoolingDataSource closes physical connections
Date Wed, 20 Jun 2007 19:48:26 GMT

    [ https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506646
] 

Phil Steitz commented on DBCP-212:
----------------------------------

PoolableConnectionFactory.makeObject() has been synchronized since the initial commit.  Synchronization
of validateObject was removed in r132110 in response to BZ 25096.  Can anyone else see a reason
that this synchronization is necessary?

> PoolingDataSource closes physical connections
> ---------------------------------------------
>
>                 Key: DBCP-212
>                 URL: https://issues.apache.org/jira/browse/DBCP-212
>             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
>             Fix For: 1.3
>
>         Attachments: DBCPtester.java, DBCPtester.java, output.txt
>
>
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message