我们希望使用XA事务来协调ActiveMQ和Hibernate（Sql Server 2008）之间的活动。
我们正在使用：
- 弹簧3.0.5
- 休眠3.6.2
- ActiveMQ 5.5.0
- Atomikos 3.7
我们看到在与尚未启动的事务相关的日志文件中生成以下错误。这些总是与JMS相关。
事务"[ID]"尚未启动。
这些一直都在日志中生成。
问题更为复杂，因为我们有3个web应用程序使用相同的JMS队列，并且当只有一个web应用软件运行时，似乎不会生成错误。
它们被部署到运行在同一台机器上的Tomcat7.0.14的单独实例中。
2011-05-31 15:04:27,065 [Atomikos:30] WARN - [com.atomikos.diagnostics.Slf4jConsole] : XA resource 'XAJMS': rollback for XID '3139322E3136382E302E35332E746D30363636333030303031:3139322E3136382E302E35332E746D36363633' raised 0: unknown
javax.transaction.xa.XAException: Transaction 'XID:1096044365:3139322e3136382e302e35332e746d30363636333030303031:3139322e3136382e302e35332e746d36363633' has not been started.
at org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:732)
at org.apache.activemq.TransactionContext.rollback(TransactionContext.java:497)
at com.atomikos.datasource.xa.XAResourceTransaction.rollback(XAResourceTransaction.java:690)
at com.atomikos.icatch.imp.RollbackMessage.send(RollbackMessage.java:72)
at com.atomikos.icatch.imp.PropagationMessage.submit(PropagationMessage.java:111)
at com.atomikos.icatch.imp.Propagator$PropagatorThread.run(Propagator.java:87)
at com.atomikos.icatch.imp.Propagator.submitPropagationMessage(Propagator.java:66)
at com.atomikos.icatch.imp.HeurHazardStateHandler.onTimeout(HeurHazardStateHandler.java:124)
at com.atomikos.icatch.imp.CoordinatorImp.alarm(CoordinatorImp.java:1105)
at com.atomikos.timing.PooledAlarmTimer.notifyListeners(PooledAlarmTimer.java:112)
at com.atomikos.timing.PooledAlarmTimer.run(PooledAlarmTimer.java:99)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.transaction.xa.XAException: Transaction 'XID:1096044365:3139322e3136382e302e35332e746d30363636333030303031:3139322e3136382e302e35332e746d36363633' has not been started.
at org.apache.activemq.broker.TransactionBroker.getTransaction(TransactionBroker.java:290)
at org.apache.activemq.broker.TransactionBroker.rollbackTransaction(TransactionBroker.java:177)
at org.apache.activemq.broker.MutableBrokerFilter.rollbackTransaction(MutableBrokerFilter.java:131)
at org.apache.activemq.broker.TransportConnection.processRollbackTransaction(TransportConnection.java:436)
at org.apache.activemq.command.TransactionInfo.visit(TransactionInfo.java:104)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:306)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:179)
at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:69)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:227)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:220)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:202)
at java.lang.Thread.run(Unknown Source)
我们的春季配置：
<Resource name="jms/ConnectionFactory"
auth="Container"
type="org.apache.activemq.ActiveMQXAConnectionFactory"
description="JMS XA Connection Factory"
factory="org.apache.activemq.jndi.JNDIReferenceFactory"
brokerURL="tcp://${activemq.server.name}:${activemq.server.port}"
brokerName="LocalActiveMQBroker" />
<bean id="atomikosConnectionFactory"
class="com.atomikos.jms.AtomikosConnectionFactoryBean"
init-method="init" destroy-method="close">
<property name="uniqueResourceName" value="XAJMS" />
<property name="xaConnectionFactory" ref="jmsConnectionFactory" />
<property name="maxPoolSize" value="40" />
</bean>
<bean id="getSomeStuffListenerAdapter"
class="org.springframework.jms.listener.adapter.MessageListenerAdapter">
<property name="delegate" ref="targetElement" />
<property name="defaultListenerMethod" value="doStuff" />
<property name="messageConverter" ref="myMessageConverter" />
</bean>
<bean id="getSomeStuffListenerContainer"
class="org.springframework.jms.listener.DefaultMessageListenerContainer"
depends-on="txManager">
<property name="connectionFactory" ref="atomikosConnectionFactory"/>
<property name="destination" ref="jmsQueue01"/>
<property name="messageListener" ref="getSomeStuffListenerAdapter" />
<property name="concurrency" value="5-10" />
<property name="transactionManager" ref="txManager" />
<property name="sessionTransacted" value="true" />
</bean>
<bean id="atomikosTransactionManager"
class="com.atomikos.icatch.jta.UserTransactionManager"
depends-on="dataSource, atomikosConnectionFactory"
init-method="init" destroy-method="close">
<property name="forceShutdown" value="false" />
</bean>
<bean id="txManager"
class="org.springframework.transaction.jta.JtaTransactionManager">
<property name="transactionManager" ref="atomikosTransactionManager" />
</bean>
好的，我们在同一台机器上使用Atomikos运行3个Tomcat web应用程序时遇到了这个问题，这些应用程序指向同一个ActiveMQ服务器。
这些应用程序在具有单独Atomikos日志文件的单独Tomcat实例中运行。
问题是XA XID（事务ID）在三个应用程序中不是唯一的，这导致ActiveMQ混淆。这是由于实例在同一台计算机上运行。
如果将Atomikos和ActiveMQ日志记录设置为TRACE。然后您可以看到，同一个XID是由两个或多个应用程序生成的。
这是因为Atomikos属性设置：com.atomicos.icatch.tm.unique_name
如果未设置此项，则在生成XID时使用机器的IP地址，这对于三个应用程序是相同的，并导致冲突。
只有当3个Tomcat应用程序启动得非常接近时，才有可能出现此问题。
因此，将com.atomicos.icatch.tm.unique_name设置为每个web应用程序都是唯一的，问题就消失了。