[
https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487735
]
Marcos Sanz commented on DBCP-212:
----------------------------------
The issue can be reproduced with pool 1.2/dbcp 1.2.1/collections 3.2. It can
also be reproduced with another driver different of jConnect.
I've isolated the source of the problem. It is the debugging line
System.out.println(connectionPool.getMaxActive());
which I had in my original code (see new attachment).
It looks as if the synchronized in GenericObjectPool.getMaxActive() method
would be originating the physical opens/closes, but I still don't know why.
> 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
> Attachments: DBCPtester.java
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
