xa

问题 Anyone can kindly tell me how to process distributed transaction within postgresql, which is also called "XA"? Is there any resources about it? Great thanks for any answer. 回答1: It looks like you are a bit confused. Generally database systems support two notions of distributed transaction types: Native distributed transactions and XA transactions. Native distributed transactions are generally between different servers of the same RDBMS. Postgres also supports this with the dblink_exec command

问题 I am trying to understand two-phase-commit and it is not clear to me when each local site executes its portion of the distributed transaction. Does that happen before the prepare messages are sent. That is does it happen before the two-phase-commit xa protocol is even run? Or does each site executes its portion of the distributed transaction after receiving the prepare message, meaning the prepare message itself also includes the transaction query to be executed? 回答1: Yes, execution happens

问题 Im writing an inbound resource adapter with JCA for a legacy EIS. The EIS does not support XA transactions. The messages however form a conversation that exist of multiple messages. Each message leads to an action that will be executed by the message endpoint. At the end of the conversation, a commit/rollback message will be received. At that moment all actions should be either committed or rolled back. Is there any way that I can manage the lifecycle myself from within the RA? 回答1:

问题 Ignite ignite = Ignition.start(); How to make this ignite instance fall into existing jta transaction.. Tried.. TransactionConfiguration transactionConfiguration = new TransactionConfiguration(); Factory factory = FactoryBuilder.factoryOf(userTransactionManager); transactionConfiguration.setTxManagerFactory(factory); transactionConfiguration.setUseJtaSynchronization(true); How to corellate these TransactionConfiguration with the instance of ignite..!! Any help..! Referred .. http:/

问题 For days our log has been full of this message 2018-06-15 12:19:23 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a983f1e:1f3aa2ff:5a09aa02:d1c08c has 1 heuristic participant(s)! 2018-06-15 12:19:23 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=46, bqual_length=36, tx_uid=0:ffff0a983f1e:1f3aa2ff:5a09aa02

问题 I am trying to move jms messages between 2 different, remote, activeMQ brokers and after a lot of reading I am using Atomikos, as I am writing a standalone application, and I am also using spring to get the whole thing working. I have the following bean javaconfig setup @Bean(name="atomikosSrcConnectionFactory") public AtomikosConnectionFactoryBean consumerXAConnectionFactory() { AtomikosConnectionFactoryBean consumerBean = new AtomikosConnectionFactoryBean(); consumerBean

问题 I have a wildfly server 8 and in the log I get periodicaly those two warnings : 2014-06-10 12:01:19,255 WARN [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000904: No security domain defined for crash recovery: java:jboss/datasources/sevicesDS 2014-06-10 12:01:19,256 WARN [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000905: Subject for crash recovery was null: java:jboss/datasources/sevicesDS my datasource config: <xa-datasource

问题 The situation is we want to use XA transactions to coordinate activity between ActiveMQ and Hibernate (Sql Server 2008). We are using: Spring 3.0.5 Hibernate 3.6.2 ActiveMQ 5.5.0 Atomikos 3.7 We are seeing the following errors getting generated in the log file related to the transaction has not been started. These are always related to JMS. Transaction '[ID]' has not been started. These are getting generated into the logs all the time. The issue is more complicated in that we have 3 web

问题 I would like to understand if the Distributed Transaction Capabilities will work for my application if I set the com.atomikos.icatch.enable_logging=false Do I understand correctly that the Transaction Recovery is relevant in the cases where there has been a crash, and we want to completely restart the same transaction. Does the recovery work within the same distributed transaction? My application is tolerant to failures in terms that a failure can always just be restarted from the start with

问题 Exception from application log: 12:04:18,503 INFO ExceptionResolver:30 - [ org.springframework.dao.DeadlockLoserDataAccessException ] Hibernate flushing: could not update: [sero.chase.integration.Beans.Bean#1000]; SQL [update SCHM.v***240u_bean set prop1=?, prop2=?, prop3=?, prop4=?, prop5=?, prop6=?, prop7=?, prop8=?, prop9=?, prop10=?, prop11=?, prop12=?, prop13=?, prop14=?, prop15=?, prop16=?, prop17=?, prop18=?, prop19=?, prop20=?, prop21=?, where bean_id=?]; UNSUCCESSFUL EXECUTION CAUSED