Null pointer exception in Oracle XA Thin Driver
S. Rochan
I am using 8.1.7 oracle database and thin driver.
The config.xml looks as below
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.xa.client.OracleXADataSource" InitialCapacity="2"
LoginDelaySeconds="2" MaxCapacity="5" Name="DataPool1"
Properties="user=user1;password=user1;url=jdbc:oracle:thin:@192.168.168.5:15
21:dbinstance"
SupportsLocalTransaction="false" Targets="adminserver"/>
<JDBCTxDataSource EnableTwoPhaseCommit="true"
JNDIName="TxDataPool1" Name="TxDataPool1"
PoolName="DataPool1" Targets="adminserver"/>
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.xa.client.OracleXADataSource" InitialCapacity="2"
LoginDelaySeconds="2" MaxCapacity="5" Name="DataPool2"
Properties="user=user2;password=user2;url=jdbc:oracle:thin:@192.168.168.5:15
21:dbinstance"
SupportsLocalTransaction="false" Targets="adminserver"/>
<JDBCTxDataSource EnableTwoPhaseCommit="true"
JNDIName="TxDataPool2" Name="TxDataPool2"
PoolName="DataPool2" Targets="adminserver"/>
I get the following error
java.sql.SQLException: ORA-29532: Java call terminated by uncaught Java
exception: java.lang.NullPointerException
ORA-06512: at "SYS.JAVA_XA", line 0
ORA-06512: at line 1
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:542)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1311)
at
oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:738)
at
oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1313
)
at
oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1
353)
at
oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1760)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:1805)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
ment.java:322)
at
oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.j
ava:366)
at
oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:102)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:324)
at
weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.ja
va:994)
at
weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.
java:947)
at
weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
ava:206)
at
weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
nsactionImpl.java:316)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:817)
at
weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:788)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:130)
at
weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:208)
at
weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
va:80)
at
weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:58
)
This happens in a place where I use prepared statement in the scope of a
transaction.
Is there any change in the way I need to use transactions.