[
https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487282
]
Phil Steitz commented on DBCP-212:
----------------------------------
Thanks. Also thanks in advance for running against pool 1.2/dbcp 1.2.1 to
verify same behavior.
The log I examined for Sybase was the server log with the (SQL Anywhere 10)
server started with the -zr option set to "SQL" or "ALL". That appears to show
connects / disconnects, as well as sp execution.
I don't know much about Sybase, but from the docs, it looks like if you can
snoop the TDS traffic, you see much more than I can from the logs.
All my tests were on Linux (Fedora Core 4) Sun JDK 1.5.0_10, JConnect 6.0.5.
I also ran against postgres, which spawns an OS process for each connection,
and verified from its logs as well as from ps output that there was no process
churn (PIDs did not change).
> 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]
