BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

Question

Hello anybody,
learnt XA being necessary if more than one sql command in transaction, so I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now I receive the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
start() failed on resource 'OracleDB' Unexpected error during start for XAResource
'OracleDB': null
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.deploy(Application.java:247)
     at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
     at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
     at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

Answer 1

Hi Klaus,
if you want to implement a global transaction over two different JDBC Resource Managers
(update on both + 2PC) they have to be both XA compliant.
Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
and configuring a TXDataSource with "enable two-phase commit" = true (but only one
non-XA JDBC driver at a time can participate in a distributed transaction).
Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
transactions or distributed transactions without XA drivers as well (using a single
resource manager).
But if you want to update multiple resource managers in the same transaction using
EJBs, this is a "global" transaction, and WL server fully supports it.
But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
Sergi
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
>
Hi Sergi, hello world,
thanks a lot for this message. So the conclusion is that I hava no chance
at all
to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
a prerequisite
for EJB are XA-transactions.
Is this conclusion correct.
Many thanks again
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
distributed transaction (XA) features require version
Oracle8i release 8.1.6 or later of the Oracle server.
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hi Sergi,
1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
2.) I didn´t use a special driver but that that was delivered with thewls
server
in the package "weblogic.jar".
Could I enable you helping me with this information?
Best wishes
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
which
1) Oracle server version (I don't think it's a 8.3.2.)
2) Oracle JDBC driver version
are you you using ?
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hello anybody,
learnt XA being necessary if more than one sql command in transaction,so
I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now
I
receive
the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating itsSQL
Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction
branch
start() failed on resource 'OracleDB' Unexpected error during start
for
XAResource
'OracleDB': null
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.deploy(Application.java:247)
     at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
     at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
     at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus