[
https://jira.jboss.org/browse/JBAS-7068?page=com.atlassian.jira.plugin.sy...
]
Michele Zinna commented on JBAS-7068:
-------------------------------------
Just to note that the method oracle.jdbc.driver.OracleConnection.pingDatabase(int timeout)
implements the timeout creating a new thread at each call. It results in performace issues
in case of heavy load.
Using "0" as timeout value no thread is created and a simple "select
'x' from dual" query test is performed.
More over this method has been deprecated, the overloaded method:
oracle.jdbc.driver.OracleConnection.pingDatabase(), could be invoked that is equivalent to
previous with "0" as timeout value.
Wrong timeout-valiue in OracleValidConnectionChecker
----------------------------------------------------
Key: JBAS-7068
URL:
https://jira.jboss.org/browse/JBAS-7068
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-5.1.0.GA
Reporter: Christian Daszenies
Assignee: Jesper Pedersen
Fix For: 6.0.0.M4
Attachments: OracleValidConnectionCheckerFixed.jar
OracleValidConnectionChecker calls
oracle.jdbc.driver.OracleConnection.pingDatabase(5000) - 5000 is used as timeout in
seconds! by pingDatabase
furthermore it would be nice if the timeout would be configurable (or at least easy to
override)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira