users@glassfish.java.net

Re: Deadlock when using connection leak tracing and reclaim

From: <forums_at_java.net>
Date: Wed, 13 Apr 2011 23:47:50 -0500 (CDT)

<jdbc-connection-pool validation-table-name="CONNECTION_TEST"
allow-non-component-callers="true"
sql-trace-listeners="com.mycompany.SQLTraceListener"
datasource-classname="com.ibm.db2.jcc.DB2XADataSource" max-pool-size="100"
connection-leak-reclaim="true" res-type="javax.sql.XADataSource"
connection-leak-timeout-in-seconds="4000" name="MyPoolTx"
is-connection-validation-required="true" ping="true"
transaction-isolation-level="read-committed"> <property name="url"
value="jdbc:db2://myserver:50000/mydb" /> <property name="serverName"
value="myserver" /> <property name="maxStatements" value="200" /> <property
name="fullyMaterializeInputStreams" value="true" /> <property
name="allowNextOnExhaustedResultSet" value="1" /> <property name="user"
value="myuser" /> <property name="progressiveStreaming" value="2" />
<property name="databaseName" value="mydb" /> <property name="driverType"
value="4" /> <property name="fullyMaterializeLobData" value="true" />
<property name="password" value="mypw" /> <property name="portNumber"
value="50000" /> <property name="progresssiveLocators" value="2" />
</jdbc-connection-pool> <jdbc-resource pool-name="MyPoolTx"
jndi-name="jdbc/dsmypooltx" /> </resources>

--
[Message sent by forum member 'mphaua']
View Post: http://forums.java.net/node/791265