April 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-516) Transaction Reaper reaps atomic JTS transactions that have already started 2PC

by Michael Musgrove (JIRA)

Transaction Reaper reaps atomic JTS transactions that have already started 2PC ------------------------------------------------------------------------------ Key: JBTM-516 URL: https://jira.jboss.org/jira/browse/JBTM-516 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.6 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.7 Start a JTS AtomicTransaction from a remote client with a timeout. During commit if a ResourceManager takes longer than the timeout period to respond then the TransactionReaper attempts a rollback even though 2PC has already started. The problem is in ArjunaTransactionImple::rollback_only (perhaps the determineStatus() check needs to compare against Status.StatusActive instead of StatusPrepared). The TM prints out the following warning: 2009-03-26 13:09:31,181 [Thread-8] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for TX -53ef7d76:dd94:49cb7e7f:3 in state RUN 2009-03-26 13:09:31,181 [Thread-9] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.arjuna.coordinator.TransactionReaper_8] - TransactionReaper::doCancellations worker Thread[Thread-9,10,main] failed to cancel TX -53ef7d76:dd94:49cb7e7f:3 -- rescheduling for mark-as-rollback 2009-03-26 13:09:31,182 [Thread-9] WARN com.arjuna.ats.jts.logging.loggerI18N - [com.arjuna.ats.internal.jts.cwcommit] Failed to mark transaction as rollback only: org.omg.CORBA.INVALID_TRANSACTION: vmcid: 0x4000 minor code: 3617 completed: No at com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple.rollback_only(ArjunaTransactionImple.java:1159) at com.arjuna.ats.internal.jts.ControlWrapper.rollback_only(ControlWrapper.java:334) at com.arjuna.ats.internal.jts.ControlWrapper.preventCommit(ControlWrapper.java:172) at com.arjuna.ats.arjuna.coordinator.TransactionReaper.doCancellations(TransactionReaper.java:691) at com.arjuna.ats.internal.arjuna.coordinator.ReaperWorkerThread.run(ReaperWorkerThread.java:91) 2009-03-26 13:09:31,184 [Thread-9] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.arjuna.coordinator.TransactionReaper_15] - TransactionReaper::doCancellations worker Thread[Thread-9,10,main] failed to mark TX -53ef7d76:dd94:49cb7e7f:3 as rollback only -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-517) Ignore abort on aborted transactions

by Mark Little (JIRA)

Ignore abort on aborted transactions ------------------------------------ Key: JBTM-517 URL: https://jira.jboss.org/jira/browse/JBTM-517 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.6 Reporter: Mark Little Assignee: Mark Little Fix For: 4.7 JTS allows us to differentiate transaction termination from other threads by throwing exceptions during termination to subsequent threads. We try to mask that in JTA because it can be counterintuitive. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-523) add get_uid to SubordinateTransaction

by Jonathan Halliday (JIRA)

add get_uid to SubordinateTransaction ------------------------------------- Key: JBTM-523 URL: https://jira.jboss.org/jira/browse/JBTM-523 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA Affects Versions: 4.6.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 The transaction bridge needs to get the tx Uid for recovery purposes. In order to do so in a JTA/JTAX portable way, the SubordinateTransaction Interface needs to support it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-524) BridgeWrapper uses wrong UnknownTransactionException

by Jonathan Halliday (JIRA)

BridgeWrapper uses wrong UnknownTransactionException ---------------------------------------------------- Key: JBTM-524 URL: https://jira.jboss.org/jira/browse/JBTM-524 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.6.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 The XTS subordinate tx support API exposes the internal version of UnknownTransactionException instead of the one from the published API jar, which causes linking problems for client apps. change import com.arjuna.mw.wst.exceptions.UnknownTransactionException; to import com.arjuna.wst.UnknownTransactionException; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-525) improve XAResourceRecord commit error logging

by Jonathan Halliday (JIRA)

improve XAResourceRecord commit error logging --------------------------------------------- Key: JBTM-525 URL: https://jira.jboss.org/jira/browse/JBTM-525 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA, JTS Affects Versions: 4.6.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 Some XAResource implementations throw non-XA exceptions, which we catch but don't always log, making some problem diagnosis difficult. Improve the exception logging, particularly for commit phase problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-515) add release tag info to builds

by Jonathan Halliday (JIRA)

add release tag info to builds ------------------------------ Key: JBTM-515 URL: https://jira.jboss.org/jira/browse/JBTM-515 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7 It would be helpful if a binary could tell which version of the source it was built from, at least if it's a tagged release. com.hp.mw.source ant property is already injected into the .properties files in the .jars. However, it's not set and does not cascade down properly from the top level build script anyhow, due to the use of the runant macro. 1) Change the build.xml script so the property is utilized correctly, then change the build-release-packages.xml so a value is set based on the svn tag. 2) Change e.g. TransactionManagerService so it uses Configuration.getBuildTimeProperty to get and print the value in the logs at AS startup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-514) SubordinationManager does not always select JTA/JTAX correctly

by Jonathan Halliday (JIRA)

SubordinationManager does not always select JTA/JTAX correctly -------------------------------------------------------------- Key: JBTM-514 URL: https://jira.jboss.org/jira/browse/JBTM-514 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration, JCA, JTA Implementation, JTS Implementation Affects Versions: 4.6 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7 SubordinationManager return an implementation of the Subordinate transaction support interfaces depending on if the system is running in JTA or JTAX mode. It chooses the right one when running standalone, but gets it wrong when embedded in AS or running some non-standard config. Improve the mechanism it uses to make a decision on which version to supply and also add setter to allow explicit programmatic override. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-519) Log version information during startup

by Jesper Pedersen (JIRA)

Log version information during startup -------------------------------------- Key: JBTM-519 URL: https://jira.jboss.org/jira/browse/JBTM-519 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Affects Versions: 4.6.0 Reporter: Jesper Pedersen Priority: Minor It would be nice if the version information was logged during startup, like: JBossTS Transaction Service (JTA version) 4.6.0.GA - JBoss Inc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2009