May 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-365) addSynchronization calls during beforeCompletion are problematic

by Steven Hawkins (JIRA)

addSynchronization calls during beforeCompletion are problematic ---------------------------------------------------------------- Key: JBTM-365 URL: http://jira.jboss.com/jira/browse/JBTM-365 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.3.0.GA Reporter: Steven Hawkins Asynch calls to com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.addSynchronization during beforeCompletion are problematic since access to _currentRecord and _synchs is unsynchronized in addSynchronization wrt beforeCompletion. This is similar to JBTM-188. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
12
0 / 0

[JBoss JIRA] Created: (JBTM-561) merge jbossts-common into jbossjta.jar/jbossjts.jar

by Jonathan Halliday (JIRA)

merge jbossts-common into jbossjta.jar/jbossjts.jar --------------------------------------------------- Key: JBTM-561 URL: https://jira.jboss.org/jira/browse/JBTM-561 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Release Process Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 As no other project consumes jbossts-common as an independent entity, it makes little sense to preserve it as such. For ease of embedding we should have all the files in a single .jar. Remove jbossts-common.jar and merge the contents into jbossjta.jar or jbossjts.jar according to distribution type. -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-562) clean up broken javadoc tags

by Jonathan Halliday (JIRA)

clean up broken javadoc tags ---------------------------- Key: JBTM-562 URL: https://jira.jboss.org/jira/browse/JBTM-562 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, JTA, JTS, Transaction Core Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 Some javadoc is broken and causes the doclet to whine annoyingly during builds. Placate 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-559) remove default properties from config file

by Jonathan Halliday (JIRA)

remove default properties from config file ------------------------------------------ Key: JBTM-559 URL: https://jira.jboss.org/jira/browse/JBTM-559 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 The jbossts-properties.xml is large and complex. There are many configuration options, but only a handful are changed from their defaults in most systems. We should remove the others from the properties file in order to reduce the clutter. -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-359) Transaction Bridging can timeout b ecause it bundles phase zero work into prepare

by Andrew Dinn (JIRA)

Transaction Bridging can timeout b ecause it bundles phase zero work into prepare --------------------------------------------------------------------------------- Key: JBTM-359 URL: http://jira.jboss.com/jira/browse/JBTM-359 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.3.0.GA Reporter: Andrew Dinn Assigned To: Andrew Dinn Fix For: 4.6 Bridged (from XTS to JTA) transaction synchronizations currently get executed at prepare time which can cause very long delays. This may cause the transaction coordinator to timeout the prepare or cause another participant to timeout. It would be better if the JTA brdge manager intercepted add synch requests and registered its own phase zero synchronization to run them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-560) provide distinct beforeCompletion phase in subordinate tx API

by Jonathan Halliday (JIRA)

provide distinct beforeCompletion phase in subordinate tx API ------------------------------------------------------------- Key: JBTM-560 URL: https://jira.jboss.org/jira/browse/JBTM-560 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA, JTA, JTS, Transaction Core Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Mark Little Fix For: 4.7.0 A subordinate transaction exposes an API that allows the prepare and commit/rollback phases of the termination protocol to be driven separately, much like a resource. This maps well to the JCA Terminator API. However, it poses difficulties for beforeCompletion work. With the current API these must be done at prepare time, but should run in transaction context, which the prepare does not necessarily do. They may also take a long time (e.g. large hibernate context flushes) which can cause timeout issues. It would be useful to extend the XATerminator so that it exposes the before (and maybe the after, although that's less important) synchronization phases as separate operations. Care should be taken that this does not break usage done though the existing JCA API, which would not allow the new methods to be used directly. -- 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-563) Tx reaper won't touch rollback only JTA tx

by Jonathan Halliday (JIRA)

Tx reaper won't touch rollback only JTA tx ------------------------------------------ Key: JBTM-563 URL: https://jira.jboss.org/jira/browse/JBTM-563 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 The reaper uses Reapable.running() to determine if a tx is in a fit state to be timed out. The impl of this method in the JTS correctly returns true for active and abort only states, but the JTA version is checking only for active, not abort only. As a result, calling setRollbackOnly and then abandoning a tx will leave it in limbo - it will never time out. This is a Bad Thing. -- 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

14 years, 11 months

1
3
0 / 0

[JBoss JIRA] Updated: (JBTM-44) Transaction bridging

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-44?page=com.atlassian.jira.plugin... ] Jonathan Halliday updated JBTM-44: ---------------------------------- Fix Version/s: 4.8.0 (was: 4.7.0) Pushing to 4.8 for ongoing work > Transaction bridging > -------------------- > > Key: JBTM-44 > URL: https://jira.jboss.org/jira/browse/JBTM-44 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA, JTS, XTS > Reporter: Mark Little > Assignee: Jonathan Halliday > Priority: Critical > Fix For: 4.8.0 > > Attachments: jbossxts-bridge.zip > > -- 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

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-297) Improve XID printing

by Mark Little (JIRA)

Improve XID printing -------------------- Key: JBTM-297 URL: http://jira.jboss.com/jira/browse/JBTM-297 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.4 Printing the byte array through String loses information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-556) remove unused TxHierarchy

by Jonathan Halliday (JIRA)

remove unused TxHierarchy ------------------------- Key: JBTM-556 URL: https://jira.jboss.org/jira/browse/JBTM-556 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.7.0 -- 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

14 years, 11 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2009