Opta SQL Driver & Connection Pooling Problem
harveyk Sep 18, 2001 11:12 AMConfiguration
JBoss 2.4.1
Opta 4.11
JDK 1.3.1
Win2K
SQL Server 7
When defining a datasource using the following settings in the JBOSS.JCML file,
connection pooling does not work -- the pool min & max sizes are ignored:
<mbean code="org.jboss.jdbc.XADataSourceLoader" name="DefaultDomain:service=XADataSource,name=Test123"> <attribute name="PoolName">Test123</attribute> <attribute name="DataSourceClass">com.inet.tds.XDataSource</attribute> <attribute name="Properties">host=xyz;database=Testing;appname=Test</attribute> <attribute name="JDBCUser">sa</attribute> <attribute name="Password">abc</attribute> <attribute name="MinSize">0</attribute> <attribute name="MaxSize">0</attribute> <attribute name="GCEnabled">true</attribute> <attribute name="GCMinIdleTime">1200000</attribute> <attribute name="GCInterval">120000</attribute> <attribute name="InvalidateOnError">false</attribute> <attribute name="TimestampUsed">false</attribute> <attribute name="Blocking">true</attribute> <attribute name="LoggingEnabled">false</attribute> <attribute name="IdleTimeoutEnabled">false</attribute> <attribute name="IdleTimeout">1800000</attribute> <attribute name="MaxIdleTimeoutPercent">1.0</attribute> </mbean>
When using the following settings in the JBOSS.JCML file,
connection pooling works:
<mbean code="org.jboss.jdbc.XADataSourceLoader" name="DefaultDomain:service=XADataSource,name=Test123"> <attribute name="PoolName">Test123</attribute> <attributename="DataSourceClass"> org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl</attribute> <attribute name="URL">jdbc:inetdae7:xyz:1433?database=Testing&appname=Test</attribute> <attribute name="JDBCUser">sa</attribute> <attribute name="Password">abc</attribute> <attribute name="MinSize">5</attribute> <attribute name="MaxSize">10</attribute> <attribute name="GCEnabled">true</attribute> <attribute name="GCMinIdleTime">500</attribute> <attribute name="GCInterval">120000</attribute> <attribute name="InvalidateOnError">false</attribute> <attribute name="TimestampUsed">false</attribute> <attribute name="Blocking">true</attribute> <attribute name="LoggingEnabled">false</attribute> <attribute name="IdleTimeoutEnabled">true</attribute> <attribute name="IdleTimeout">500</attribute> <attribute name="MaxIdleTimeoutPercent">1.0</attribute> </mbean>
The only differences between the two methods are as follows:
1. Use the Org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl class and not the com.inet.tds.XDataSource class.
2. Use the URL attribute to specify DSN properties as opposed to the Properties