June 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-225) Potential race condition in top-down/bottom-up recovery with XA_RETRY

by Mark Little (JIRA)

Potential race condition in top-down/bottom-up recovery with XA_RETRY --------------------------------------------------------------------- Key: JBTM-225 URL: http://jira.jboss.com/jira/browse/JBTM-225 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Affects Versions: 4.2.3.SP4 Reporter: Mark Little Assigned To: Mark Little -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-499) LRCO update

by Mark Little (JIRA)

LRCO update ----------- Key: JBTM-499 URL: https://jira.jboss.org/jira/browse/JBTM-499 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Work to pass intentions list processing to local db transaction done in scope of partner effort but not checked in. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-413) Support original LRCO implementation

by Mark Little (JIRA)

Support original LRCO implementation ------------------------------------ Key: JBTM-413 URL: https://jira.jboss.org/jira/browse/JBTM-413 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-368) Check lifetime of transactions during recovery

by Mark Little (JIRA)

Check lifetime of transactions during recovery ---------------------------------------------- Key: JBTM-368 URL: http://jira.jboss.com/jira/browse/JBTM-368 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery Reporter: Mark Little -- 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, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (JBTM-398) Compile list of refactor/consolidation options with existing code.

by Mark Little (JIRA)

Compile list of refactor/consolidation options with existing code. ------------------------------------------------------------------ Key: JBTM-398 URL: https://jira.jboss.org/jira/browse/JBTM-398 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation, Transaction Core, WS-T Implementation Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-528) Periodic commit retry

by Mark Little (JIRA)

Periodic commit retry --------------------- Key: JBTM-528 URL: https://jira.jboss.org/jira/browse/JBTM-528 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.0 XA_RETRY on commit ... /* * Could do timeout retry here, but that could cause other resources in the list to go down the * heuristic path (some are far too keen to do this). Fail and let recovery retry. Meanwhile * the coordinator will continue to commit the other resources immediately. */ -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-251) Check conformance and compatibility of two JTA implementations

by Mark Little (JIRA)

Check conformance and compatibility of two JTA implementations -------------------------------------------------------------- Key: JBTM-251 URL: http://jira.jboss.com/jira/browse/JBTM-251 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Make sure that both of our JTA implementations behave as similarly as possible from an interface perspective. For example, that timeouts are handled the same. Some differences are bound to be visible because the two implementations have different capabilities. But ignoring those, we need to be as consistent as possible. -- 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, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (JBTM-336) crash recovery testing with AS integration

by Jonathan Halliday (JIRA)

crash recovery testing with AS integration ------------------------------------------ Key: JBTM-336 URL: http://jira.jboss.com/jira/browse/JBTM-336 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3.0.BETA2 Reporter: Jonathan Halliday Fix For: 4.4 Current testing of JBossTS is standalone. The JBossAS integration code does not get exercised. This a particularly a problem for specialized crash recovery modules that are used only when running integrated with AS. Work with the AS team to figure out how best to do crash recovery testing for JBossAS. -- 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, 5 months

2
13
0 / 0

[JBoss JIRA] Created: (JBTM-489) WS-T 1.1. implementation is generating invalid faults

by Andrew Dinn (JIRA)

WS-T 1.1. implementation is generating invalid faults ----------------------------------------------------- Key: JBTM-489 URL: https://jira.jboss.org/jira/browse/JBTM-489 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn The WS-C 1.1. spec employs a slightly different set of SOAP fault codes to the 1.0 implementation. The current 1.1. implementation is still generating faults included in the 1.0 set but not in the 1.1 set, for example, NO_ACTIVITY. This may lead to interopability issues. All fault cases should be checked and, where necessary, corrected to generate faults which conform to the specification. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-530) Thrown Exceptions often loose the original cause

by Davide Cavestro (JIRA)

Thrown Exceptions often loose the original cause ------------------------------------------------ Key: JBTM-530 URL: https://jira.jboss.org/jira/browse/JBTM-530 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5.0 Reporter: Davide Cavestro In JBossTM exceptions are often catched and left behind in favor of a new dedicated Exception (or Error) contextually thrown. This lead to a steady lack of information about the origin of the final symptom. As an example, see the following code snippet (extracted from com.arjuna.ats.internal.arjuna.objectstore.JDBCStore.JDBCStore()) ... try { initialise(""); } catch (Exception e) { throw new ObjectStoreError(); } ... Here the original exception "e" is lost in favor of a new ObjectStoreError. No one will never know the cause of the thrown ObjectStoreError, nor see what's wrong without using a debugger (if ever available). Since I saw the binary distribution of JBossTM (at least version 4.5.0) is compiled for Java 1.5, I suppose you aren't denied to use the standard exception chaining mechanism introduced since Java 1.4 (namely the java.lang.Throwable.cause field) Please consider refactoring your code to chain the exception causes. It would be very useful. -- 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, 9 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 June 2009