Sample below works fine (at least for me: JBoss4.2.1.GA Oracle 10g) ... | <xa-datasource> | <jndi-name>XAOracleDS</jndi-name> | <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:@ORA_HOST:1521:ORA_SVC</xa-datasource-property> | <xa-datasource-property name="User">jboss</xa-datasource-property> | <xa-datasource-property name="Password">*****</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/> | | <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml --> | <metadata> | <type-mapping>Oracle9i</type-mapping> | </metadata> | <min-pool-size>1</min-pool-size> | <max-pool-size>10</max-pool-size> | <blocking-timeout-millis>5000</blocking-timeout-millis> | <idle-timeout-minutes>2</idle-timeout-minutes> | </xa-datasource> | ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097330#4097330 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097330 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
