Is double JDBC connection pool to Oracle (no-tx-separate-pools) required in JBoss EAP

Solution Verified - Updated -

Issue

  • We are upgrading our environment to Oracle JDBC driver 11.2.0.3 and would like to know if we have to use the <no-tx-separate-pools /> attribute for that version as well. In which situations do we have to use the "<no-tx-separate-pools />" parameter when setting up xa-datasources? We would like to remove the parameter due to the double connection pool it creates. Configuration example:
        <xa-datasource>
             ...
             <no-tx-separate-pools />
             <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>
             <metadata>
                  <type-mapping>Oracle9i</type-mapping>
             </metadata>
             ...
        </xa-datasource>

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4.x
    • 5.x
    • 6.x
    • 7.x
  • Oracle JDBC Driver
    • 9.x
    • 10.x
    • 11.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content