[
https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487235
]
Marcos Sanz commented on DBCP-212:
----------------------------------
Yes, the test has been made with Commons Pool 1.3
It is possible to determine that connections are being physically
closed/reopened in that the process IDs and the login dates at the
master..sysprocesses table in the database server are continuously changing for
this application's connections. The number of connections is not stable = 15
either, it varies between 12-15.
I'll rerun the tests on Tuesday with older versions of pool/dbcp. I'll try to
capture some TDS traffic with RIBO, as well.
You wrote "I examined the connection logs". Is there some debug-switch I can
turn on and that would help you debugging?
> 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]
