When to configure an XA datasource?
4425 단어 Oaclejbossxa-datasource
WARN [TxConnectionManager] Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure.
It's relevant to JBoss Transaction Management Service for multiple datasources. That is, you have multiple datasources configured and your transactions span multiple data sources. In this case, you need to configure them as XA datasources so that JBoss would not complain.
This is often the case when using Oracle, as you can have multiple users/schema in one database. My test showed this is when XA datasources should be configured.
For instance, we can have two users "BILLING" and "LOG" in one Oracle database. We need to configure two datasources for each of them. If transactions span across these two users, we need to configure xa-datasources:
<xa-datasource>
<jndi-name>BILLINGDS_XA</jndi-name>
<track-connection-by-tx>true</track-connection-by-tx>
<isSameRM-override-value>false</isSameRM-override-value>
<managedconnectionfactory-class>org.jboss.resource.adapter.jdbc.xa.oracle.XAOracle ManagedConnectionFactory</managedconnectionfactory-class>
<transaction-isolation></transaction-isolation>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
<xa-datasource-property name="URL">jdbc:oracle:thin:@dbserverIP:1521:SID</xa-datasource-property>
<xa-datasource-property name="User">BILLING</xa-datasource-property>
<xa-datasource-property name="Password">passwordOfBILLING</xa-datasource-property>
<min-pool-size>5</min-pool-size>
<max-pool-size>10</max-pool-size>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.Oracle ExceptionSorter</exception-sorter-class-name>
<mbean code="org.jboss.resource.adapter.jdbc.xa.oracle.Or acleXAExceptionFormatter" name="jboss.jca:service=OracleXAExceptionFormatter">
<depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
</mbean>
</xa-datasource>
<xa-datasource>
<jndi-name>LOGDS_XA</jndi-name>
<track-connection-by-tx>true</track-connection-by-tx>
<isSameRM-override-value>false</isSameRM-override-value>
<managedconnectionfactory-class>org.jboss.resource.adapter.jdbc.xa.oracle.XAOracle ManagedConnectionFactory</managedconnectionfactory-class>
<transaction-isolation></transaction-isolation>
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
<xa-datasource-property name="URL">jdbc:oracle:thin:@dbserverIP:1521:SID</xa-datasource-property>
<xa-datasource-property name="User">LOG</xa-datasource-property>
<xa-datasource-property name="Password">passwdOfLOG</xa-datasource-property>
<min-pool-size>5</min-pool-size>
<max-pool-size>10</max-pool-size>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.Oracle ExceptionSorter</exception-sorter-class-name>
<mbean code="org.jboss.resource.adapter.jdbc.xa.oracle.Or acleXAExceptionFormatter" name="jboss.jca:service=OracleXAExceptionFormatter">
<depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
</mbean>
</xa-datasource>
Another point is that
javax.transaction.UserTransactiion is the JTA api for explicit management of transaction boundaries. This api cannot work properly without JBoss transaction management service turned on. That is, it only works with local-tx-datasource and xa-datasource configurations, not no-tx-datasource. Since it's part of the container's (JBoss for example) Transaction Management Service.
이 내용에 흥미가 있습니까?
현재 기사가 여러분의 문제를 해결하지 못하는 경우 AI 엔진은 머신러닝 분석(스마트 모델이 방금 만들어져 부정확한 경우가 있을 수 있음)을 통해 가장 유사한 기사를 추천합니다:
자바 작업 은 Clob 또는 NClob 데이터 형식의 저장 프로 세 스 인 스 턴 스 를 포함 합 니 다.텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
CC BY-SA 2.5, CC BY-SA 3.0 및 CC BY-SA 4.0에 따라 라이센스가 부여됩니다.