Hi all,
after change from local-tx-datasource to xa-datasource an error during deploy tablecreation occur.
With local-tx-datasource at the same DB it will work fine.
ERROR [JDBCCommand] Exception caught executing SQL
java.sql.SQLException: ORA-02089: COMMIT ist nicht erlaubt in einer untergeordneten Session
(Means => COMMIT not allowed in sub-session)
no table was created but the Beans are deployed.
The XA configuration is the example from JBoss with changed URI (JDBC), the jboss-service.xml PAD is changed to TRUE
<datasources>
<xa-datasource>
<jndi-name>easy_DB</jndi-name>
<track-connection-by-tx>true</track-connection-by-tx>
<isSameRM-override-value>false</isSameRM-override-value>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
<xa-datasource-property name="URL">jdbc:oracle:thin:@localhost:1521:ORCL</xa-datasource-property>
<xa-datasource-property name="User">pbs_zds</xa-datasource-property>
<xa-datasource-property name="Password">local</xa-datasource-property>
<!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
<!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
<!-- Checks the Oracle error codes and messages for fatal errors -->
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<!-- Oracles XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction and vice-versa -->
<no-tx-separate-pools/>
</xa-datasource>
<mbean code="org.jboss.resource.adapter.jdbc.xa.oracle.OracleXAExceptionFormatter"
name="jboss.jca:service=OracleXAExceptionFormatter">
<depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
</mbean>
</datasources>
Thanks for reply
Wolf
