Internal error: Cannot obtain XAConnection

Question

I am porting my application from WL8.1-SQl2000 to Sql Server2005. I went in for the Microsoft’s <i><b>MS SQL Server Driver(Type 4 XA) Versions:2000</b></i> and the corresponding one for non-XA also. Then in the next step where we usually give the other DB properties like DB name, server name etc, there is a field called “Properties” which defines the basic properties which we have configured. In that field, there is a new property having name-value pair : dataSourceName=SQL2000JDBC. I am not sure what this would do, so I just left it to remain & continued with the other things.
This, in no way affected the proper execution of my application.
I have 1 XA datasource & 3 non-XA datasources configured for my application.
When I start my server, in the comman prompt, a resource limit exception appears & then the server proceeds to start successfully. I am also abe to save things into the DB & do all other tests properly. But this keeps hindering me. Our DB server is configured to accept infinite connections, so its absurd to get a connection not available exception.
I doubt whether the initial datasource property that I have mentioned can have anything to do with this exception during startup. Please help me.
Exception trace:
<Nov 15, 2006 12:29:34 PM EST> <Warning> <JDBC> <BEA-001064> <Ignoring property
'enableTwoPhaseCommit' for JDBCTxDataSource "TweDS". This property is used only
for those drivers that do not natively support XA.>
java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.commo
n.resourcepool.ResourceLimitException: No resources currently available in pool
ITestPool to allocate to applications, please increase the size of the pool and
retry..
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
315)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:305)
at com.taxware.twe.util.SQLConnection.getConnection(SQLConnection.java:1
68)
at com.taxware.twe.audit.AuditStartUp.main(AuditStartUp.java:333)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.j
ava:229)
at
weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.
java:160)
at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.j
ava:36)

Answer 1

charu s wrote:
I am porting my application from WL8.1-SQl2000 to Sql Server2005. I went in for the Microsoft???
s <i><b>MS SQL Server Driver(Type 4 XA) Versions:2000</b></i> and the corresponding one for non-XA also. Then in the next step where we usually give the other DB properties like DB name, server name etc, there is a field called ???Properties??? which defines the basic properties which we have configured. In that field, there is a new property having name-value pair : dataSourceName=SQL2000JDBC. I am not sure w
hat this would do, so I just left it to remain & continued with the other things.
This, in no way affected the proper execution of my application.
I have 1 XA datasource & 3 non-XA datasources configured for my application.
When I start my server, in the comman prompt, a resource limit exception appears & then the server proceeds to start successfully. I am also abe to save things into the DB & do all other tests properly. But this keeps hindering me. Our DB server is configured to accept infinite connections, so its absurd to get a connection not available exception.
I doubt whether the initial datasource property that I have mentioned can have anything to do with this exception during startup. Please help me.
The pool's max capacity is defined as lower than the need at
the time. Please show me the full pool definition from the
config.xml. It may also have something to do with the fact
that your code is a startup class, and are you sure the
pool is ready at this time?
Joe
Exception trace:
<Nov 15, 2006 12:29:34 PM EST> <Warning> <JDBC> <BEA-001064> <Ignoring property
'enableTwoPhaseCommit' for JDBCTxDataSource "TweDS". This property is used only
for those drivers that do not natively support XA.>
java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.commo
n.resourcepool.ResourceLimitException: No resources currently available in pool
ITestPool to allocate to applications, please increase the size of the pool and
retry..
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
315)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
ce.java:305)
at com.taxware.twe.util.SQLConnection.getConnection(SQLConnection.java:1
68)
at com.taxware.twe.audit.AuditStartUp.main(AuditStartUp.java:333)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.t3.srvr.StartupClassService.invokeMain(StartupClassService.j
ava:229)
at
weblogic.t3.srvr.StartupClassService.invokeClass(StartupClassService.
java:160)
at weblogic.t3.srvr.StartupClassService.access$000(StartupClassService.j
ava:36)