[JBoss JIRA] (JBTM-1374) JDBC Object Store Deadlock potential with MySQL
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1374?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1374:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/192
> JDBC Object Store Deadlock potential with MySQL
> -----------------------------------------------
>
> Key: JBTM-1374
> URL: https://issues.jboss.org/browse/JBTM-1374
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Gytis Trikleris
> Assignee: Tom Jenkinson
> Fix For: 4.17.4, 5.0.0.Final
>
> Attachments: LockRecord_Thread_Test036a.zip
>
>
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_lockrecord test failed on jbossts-branch417-EAP61-java6-jdbcobjectstore
> See: http://172.17.131.2/job/jbossts-branch417-EAP61-java6-jdbcobjectstore/20/
> Failed tests:
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_lockrecord
> performing command: /usr/local/jdk1.6.0_37/bin/java -classpath dist/narayana-full-4.17.4.Final-SNAPSHOT/etc/:dist/narayana-full-4.17.4.Final-SNAPSHOT/lib/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/lib/ext/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/jacorb/lib/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/jacorb/etc/:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:../build/extlib/emma.jar:../build/extlib/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=2 -DCoordinatorEnvironmentBean.defaultTimeout=240 -Demma.coverage.out.file=./testoutput/txcore_lockrecord/LockRecord_Thread_Test036a/emptyObjectStore-coverage.ec -DportOffsetId=0 -DObjectStoreBaseDir=/home/hudson/workspace/jbossts-branch417-EAP61-java6-jdbcobjectstore/qa/testoutput/txcore_lockrecord/LockRecord_Thread_Test036a/emptyObjectStore -DRecoveryEnvironmentBean.recoveryListener=true -DObjectStoreEnvironmentBean.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.tablePrefix=Action -DObjectStoreEnvironmentBean.stateStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.stateStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.stateStore.tablePrefix=stateStore -DObjectStoreEnvironmentBean.communicationStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.communicationStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.communicationStore.tablePrefix=Communication org.jboss.jbossts.qa.Utils.EmptyObjectStore
> starting command: /usr/local/jdk1.6.0_37/bin/java -classpath dist/narayana-full-4.17.4.Final-SNAPSHOT/etc/:dist/narayana-full-4.17.4.Final-SNAPSHOT/lib/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/lib/ext/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/jacorb/lib/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/jacorb/etc/:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:../build/extlib/emma.jar:../build/extlib/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=2 -DCoordinatorEnvironmentBean.defaultTimeout=240 -Demma.coverage.out.file=./testoutput/txcore_lockrecord/LockRecord_Thread_Test036a/client_0-coverage.ec -DportOffsetId=1 -DObjectStoreBaseDir=/home/hudson/workspace/jbossts-branch417-EAP61-java6-jdbcobjectstore/qa/testoutput/txcore_lockrecord/LockRecord_Thread_Test036a/client_0 -DRecoveryEnvironmentBean.recoveryListener=true -DObjectStoreEnvironmentBean.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.tablePrefix=Action -DObjectStoreEnvironmentBean.stateStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.stateStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.stateStore.tablePrefix=stateStore -DObjectStoreEnvironmentBean.communicationStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.communicationStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.communicationStore.tablePrefix=Communication org.jboss.jbossts.qa.ArjunaCore.LockManager.client.WorkerClient003 10 10 10
> performing command: /usr/local/jdk1.6.0_37/bin/java -classpath dist/narayana-full-4.17.4.Final-SNAPSHOT/etc/:dist/narayana-full-4.17.4.Final-SNAPSHOT/lib/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/lib/ext/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/jacorb/lib/*:dist/narayana-full-4.17.4.Final-SNAPSHOT/jacorb/etc/:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:../build/extlib/emma.jar:../build/extlib/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=2 -DCoordinatorEnvironmentBean.defaultTimeout=240 -Demma.coverage.out.file=./testoutput/txcore_lockrecord/LockRecord_Thread_Test036a/emptyObjectStore-coverage.ec -DportOffsetId=2 -DObjectStoreBaseDir=/home/hudson/workspace/jbossts-branch417-EAP61-java6-jdbcobjectstore/qa/testoutput/txcore_lockrecord/LockRecord_Thread_Test036a/emptyObjectStore -DRecoveryEnvironmentBean.recoveryListener=true -DObjectStoreEnvironmentBean.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.tablePrefix=Action -DObjectStoreEnvironmentBean.stateStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.stateStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.stateStore.tablePrefix=stateStore -DObjectStoreEnvironmentBean.communicationStore.objectStoreType=com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore -DObjectStoreEnvironmentBean.communicationStore.jdbcAccess=com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess;ClassName=com.mysql.jdbc.jdbc2.optional.MysqlDataSource;DatabaseName=jbossts;ServerName=tywin.buildnet.ncl.jboss.com;PortNumber=3306;User=dtf11;Password=dtf11 -DObjectStoreEnvironmentBean.communicationStore.tablePrefix=Communication org.jboss.jbossts.qa.Utils.EmptyObjectStore
> Testcase: LockRecord_Thread_Test036a took 22.69 sec
> FAILED
> task client_0 printed Failed.
> junit.framework.AssertionFailedError: task client_0 printed Failed.
> at org.jboss.jbossts.qa.junit.TaskImpl$TaskReaderThread.checkPassFail(TaskImpl.java:671)
> at org.jboss.jbossts.qa.junit.TaskImpl.waitFor(TaskImpl.java:430)
> at org.jboss.jbossts.qa.junit.TestGroupBase.startAndWaitForClient(TestGroupBase.java:127)
> at org.jboss.jbossts.qa.junit.testgroup.TestGroup_txcore_lockrecord.LockRecord_Thread_Test036a(TestGroup_txcore_lockrecord.java:467)
> at org.jboss.jbossts.qa.junit.QATestNameRule$1.evaluate(QATestNameRule.java:89)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1412) testRecoverInflightTransaction failure (and others)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1412?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1412:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/195
> testRecoverInflightTransaction failure (and others)
> ---------------------------------------------------
>
> Key: JBTM-1412
> URL: https://issues.jboss.org/browse/JBTM-1412
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M2
> Environment: Raspberry Pi.
> java version "1.7.0_10"
> Java(TM) SE Runtime Environment (build 1.7.0_10-b18)
> Java HotSpot(TM) Client VM (build 23.6-b04, mixed mode)
> Latest "head" from repo.
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> At least three failures, but due to the verbosity of the build at this point it is hard for me to say the cause of the other two failures.
> [main] TestResource (1000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >] Flags=0
> [main] TestResource (2000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >] Flags=0
> [main] ProxyXAResource (1000:2000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (1000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >] Flags=67108864
> [main] TestResource (1000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] ProxyXAResource (1000:2000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (2000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >] Flags=67108864
> [main] TestResource (2000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_PREPARED
> [main] TestResource (1000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (2000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_COMMITED
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Tests run: 16, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4,065.677 sec <<< FAILURE!
> Results :
> Failed tests: testRecoverInflightTransaction(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): Servers were not aborted
> testRecovery(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): Servers were not aborted
> testOnePhaseCommit(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): 3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1412) testRecoverInflightTransaction failure (and others)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1412?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1412:
--------------------------------
Fix Version/s: 5.0.0.M2
> testRecoverInflightTransaction failure (and others)
> ---------------------------------------------------
>
> Key: JBTM-1412
> URL: https://issues.jboss.org/browse/JBTM-1412
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M2
> Environment: Raspberry Pi.
> java version "1.7.0_10"
> Java(TM) SE Runtime Environment (build 1.7.0_10-b18)
> Java HotSpot(TM) Client VM (build 23.6-b04, mixed mode)
> Latest "head" from repo.
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M2
>
>
> At least three failures, but due to the verbosity of the build at this point it is hard for me to say the cause of the other two failures.
> [main] TestResource (1000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >] Flags=0
> [main] TestResource (2000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >] Flags=0
> [main] ProxyXAResource (1000:2000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (1000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >] Flags=67108864
> [main] TestResource (1000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] ProxyXAResource (1000:2000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (2000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >] Flags=67108864
> [main] TestResource (2000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_PREPARED
> [main] TestResource (1000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (2000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_COMMITED
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Tests run: 16, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4,065.677 sec <<< FAILURE!
> Results :
> Failed tests: testRecoverInflightTransaction(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): Servers were not aborted
> testRecovery(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): Servers were not aborted
> testOnePhaseCommit(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): 3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1412) testRecoverInflightTransaction failure (and others)
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1412?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1412:
-------------------------------------
I think the test didn't have long enough to crash and be detected, it was set for 5 seconds but the fact your build of JTA takes an hour tells me that node is sloooow ;)
I have given it a minute now (5 seconds x 20 attempts), hopefully that will be enough.
The other failures are cascading off that one but I fixed that now too (was using @AfterClass rather than @After - d'oh)
If you want to test this, the following will get you to my code and run the integration unit tests:
git remote add tomjenkinson git://github.com/tomjenkinson/jbosstm.git
git fetch tomjenkinson
git checkout -b JBTM-1412 tomjenkinson/JBTM-1412
./build.sh -f ArjunaJTS/integration/pom.xml
(Assuming you are relatively current with master, if you are quite out of date it will be worth a full build)
> testRecoverInflightTransaction failure (and others)
> ---------------------------------------------------
>
> Key: JBTM-1412
> URL: https://issues.jboss.org/browse/JBTM-1412
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M2
> Environment: Raspberry Pi.
> java version "1.7.0_10"
> Java(TM) SE Runtime Environment (build 1.7.0_10-b18)
> Java HotSpot(TM) Client VM (build 23.6-b04, mixed mode)
> Latest "head" from repo.
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> At least three failures, but due to the verbosity of the build at this point it is hard for me to say the cause of the other two failures.
> [main] TestResource (1000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >] Flags=0
> [main] TestResource (2000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >] Flags=0
> [main] ProxyXAResource (1000:2000) XA_START [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (1000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >] Flags=67108864
> [main] TestResource (1000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] ProxyXAResource (1000:2000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (2000) XA_END [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >] Flags=67108864
> [main] TestResource (2000) XA_PREPARE [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_PREPARED
> [main] TestResource (1000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:5, subordinatenodename=null, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:3e8:50e505c6:9, subordinatenodename=null, eis_name=ProxyXAResource: 1000 2000 >]
> [main] TestResource (2000) XA_COMMIT [< formatId=131077, gtrid_length=32, bqual_length=64, tx_uid=0:ffff7f000101:3e8:50e505c6:4, node_name=1000, branch_uid=0:ffff7f000101:7d0:50e50664:5, subordinatenodename=2000, eis_name=unknown eis name >]
> [main] ProxyXAResource (1000:2000) XA_COMMITED
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Jan 03, 2013 4:17:52 AM com.arjuna.ats.jbossatx.jta.RecoveryManagerService stop
> INFO: ARJUNA032014: Stopping transaction recovery manager
> Tests run: 16, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4,065.677 sec <<< FAILURE!
> Results :
> Failed tests: testRecoverInflightTransaction(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): Servers were not aborted
> testRecovery(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): Servers were not aborted
> testOnePhaseCommit(com.arjuna.ats.jta.distributed.SimpleIsolatedServers): 3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Comment: was deleted
(was: Currently it's very difficult to reason about what the TXF subsytem needs as it's combined with the XTS substem. As an initial step I'm pulling out the TXF code into its own subsystem.)
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h2. Components and their subsystem requirements:
> h5. Transactions
> * To Investigate
>
> h5. XTS
> * Bootstrap coordinator
> * Setup WS endpoints for coordinator
> * Setup WS endpoints for the participants
> * Respond to configuration from standalone-xts.xml
> h5. REST-TX
> * Boostrap the coordinator
> * Setup a REST endpoint for the coordinator
> * Setup a REST endpoint for the participants
> h5. Blacktie
> * Register MDB
> * Register MBean
> h5. STM
> * To Investigate
> h5. TXF
> * Modify the WS handler chain on application deployment
> * Registers a CDI extension
> h2. Notable Dependencies
> h5. TXF
> * Weld
> * JBossWS
> h2. Subsystem Breakdown
> Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
> h5. Transactions
> * All current stuff
> * STM
> * TXF
> h5. XTS
> * All Current Stuff
> h5. RTS (new)
> h5. Blacktie (new)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1421) Seperate TXFramework into seperate Subsystem
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1421?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1421:
--------------------------------
Description: Currently it's very difficult to reason about what the TXF subsytem needs as it's combined with the XTS substem. As an initial step I'm pulling out the TXF code into its own subsystem.
> Seperate TXFramework into seperate Subsystem
> --------------------------------------------
>
> Key: JBTM-1421
> URL: https://issues.jboss.org/browse/JBTM-1421
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
>
> Currently it's very difficult to reason about what the TXF subsytem needs as it's combined with the XTS substem. As an initial step I'm pulling out the TXF code into its own subsystem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h5. TXF
* Weld
* JBossWS
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
was:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h2. Components and their subsystem requirements:
> h5. Transactions
> * To Investigate
>
> h5. XTS
> * Bootstrap coordinator
> * Setup WS endpoints for coordinator
> * Setup WS endpoints for the participants
> * Respond to configuration from standalone-xts.xml
> h5. REST-TX
> * Boostrap the coordinator
> * Setup a REST endpoint for the coordinator
> * Setup a REST endpoint for the participants
> h5. Blacktie
> * Register MDB
> * Register MBean
> h5. STM
> * To Investigate
> h5. TXF
> * Modify the WS handler chain on application deployment
> * Registers a CDI extension
> h2. Notable Dependencies
> h5. TXF
> * Weld
> * JBossWS
> h2. Subsystem Breakdown
> Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
> h5. Transactions
> * All current stuff
> * STM
> * TXF
> h5. XTS
> * All Current Stuff
> h5. RTS (new)
> h5. Blacktie (new)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
was:
h2. Components and their subsystem requirements:
h4. Transactions
To Investigate
h5. XTS
Bootstrap coordinator
Setup WS endpoints for coordinator
Setup WS endpoints for the participants
Respond to configuration from standalone-xts.xml
REST-TX
Boostrap the coordinator
Setup a REST endpoint for the coordinator
Setup a REST endpoint for the participants
Blacktie
Register MDB
Register MBean
STM?
TXFramework
Modify the WS handler chain on application deployment
Registers a CDI extension
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h2. Components and their subsystem requirements:
> h5. Transactions
> * To Investigate
>
> h5. XTS
> * Bootstrap coordinator
> * Setup WS endpoints for coordinator
> * Setup WS endpoints for the participants
> * Respond to configuration from standalone-xts.xml
> h5. REST-TX
> * Boostrap the coordinator
> * Setup a REST endpoint for the coordinator
> * Setup a REST endpoint for the participants
> h5. Blacktie
> * Register MDB
> * Register MBean
> h5. STM
> * To Investigate
> h5. TXF
> * Modify the WS handler chain on application deployment
> * Registers a CDI extension
> h2. Notable Dependencies
> h2. Subsystem Breakdown
> Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
> h5. Transactions
> * All current stuff
> * STM
> * TXF
> h5. XTS
> * All Current Stuff
> h5. RTS (new)
> h5. Blacktie (new)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description:
h2. Components and their subsystem requirements:
h4. Transactions
To Investigate
h5. XTS
Bootstrap coordinator
Setup WS endpoints for coordinator
Setup WS endpoints for the participants
Respond to configuration from standalone-xts.xml
REST-TX
Boostrap the coordinator
Setup a REST endpoint for the coordinator
Setup a REST endpoint for the participants
Blacktie
Register MDB
Register MBean
STM?
TXFramework
Modify the WS handler chain on application deployment
Registers a CDI extension
was:
h2. Components and their subsystem requirements:
h4. Transactions
XTS
Bootstrap coordinator
Setup WS endpoints for coordinator
Setup WS endpoints for the participants
Respond to configuration from standalone-xts.xml
REST-TX
Boostrap the coordinator
Setup a REST endpoint for the coordinator
Setup a REST endpoint for the participants
Blacktie
Register MDB
Register MBean
STM?
TXFramework
Modify the WS handler chain on application deployment
Registers a CDI extension
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h2. Components and their subsystem requirements:
> h4. Transactions
> To Investigate
>
> h5. XTS
> Bootstrap coordinator
> Setup WS endpoints for coordinator
> Setup WS endpoints for the participants
> Respond to configuration from standalone-xts.xml
> REST-TX
> Boostrap the coordinator
> Setup a REST endpoint for the coordinator
> Setup a REST endpoint for the participants
> Blacktie
> Register MDB
> Register MBean
> STM?
> TXFramework
> Modify the WS handler chain on application deployment
> Registers a CDI extension
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description:
h2. Components and their subsystem requirements:
h4. Transactions
XTS
Bootstrap coordinator
Setup WS endpoints for coordinator
Setup WS endpoints for the participants
Respond to configuration from standalone-xts.xml
REST-TX
Boostrap the coordinator
Setup a REST endpoint for the coordinator
Setup a REST endpoint for the participants
Blacktie
Register MDB
Register MBean
STM?
TXFramework
Modify the WS handler chain on application deployment
Registers a CDI extension
was:
h1. Components and their subsystem requirements:
h2. Transactions
XTS
Bootstrap coordinator
Setup WS endpoints for coordinator
Setup WS endpoints for the participants
Respond to configuration from standalone-xts.xml
REST-TX
Boostrap the coordinator
Setup a REST endpoint for the coordinator
Setup a REST endpoint for the participants
Blacktie
Register MDB
Register MBean
STM?
TXFramework
Modify the WS handler chain on application deployment
Registers a CDI extension
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h2. Components and their subsystem requirements:
> h4. Transactions
>
> XTS
> Bootstrap coordinator
> Setup WS endpoints for coordinator
> Setup WS endpoints for the participants
> Respond to configuration from standalone-xts.xml
> REST-TX
> Boostrap the coordinator
> Setup a REST endpoint for the coordinator
> Setup a REST endpoint for the participants
> Blacktie
> Register MDB
> Register MBean
> STM?
> TXFramework
> Modify the WS handler chain on application deployment
> Registers a CDI extension
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months