atomikos几个坑:
jta.properties:
com.atomikos.icatch.output_dir=/datayes/atomikos
com.atomikos.icatch.log_base_dir=/datayes/atomikos
若一个tomcat上有两个atomikos应用,则两个应用不要公用同一位置
datasource的用户名密码url不对,应用启动会失败
MySQL XA bug
Some users have reported problems with MySQL XA (related to this MySQL bug: http://bugs.mysql.com/bug.php?id=27832external). This problem only happens if you access the same MySQL database more than once in the same transaction. A workaround can be setting the following property in jta.properties:
com.atomikos.icatch.serial_jta_transactions=false
Also, make sure to set the following property on the MySQL datasource:
pinGlobalTxToPhysicalConnection="true"
MariaDB's java driver also supports this workaround since v.1.1.8
jta.properties:
com.atomikos.icatch.output_dir=/datayes/atomikos
com.atomikos.icatch.log_base_dir=/datayes/atomikos
若一个tomcat上有两个atomikos应用,则两个应用不要公用同一位置
datasource的用户名密码url不对,应用启动会失败
MySQL XA bug
Some users have reported problems with MySQL XA (related to this MySQL bug: http://bugs.mysql.com/bug.php?id=27832external). This problem only happens if you access the same MySQL database more than once in the same transaction. A workaround can be setting the following property in jta.properties:
com.atomikos.icatch.serial_jta_transactions=false
Also, make sure to set the following property on the MySQL datasource:
pinGlobalTxToPhysicalConnection="true"
MariaDB's java driver also supports this workaround since v.1.1.8