jbossts-issues March 2009

jbossts-issues@lists.jboss.org

1 participants
105 discussions

[JBoss JIRA] Created: (JBTM-508) doOnePhaseCommit raise HeuristicHazard

by Mark Little (JIRA)

doOnePhaseCommit raise HeuristicHazard -------------------------------------- Key: JBTM-508 URL: https://jira.jboss.org/jira/browse/JBTM-508 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 Should raise HeuristicHazard as per OTS. Throws HeuristicRollbackException instead. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-506) jtax subordinate TransactionImple confuses TwoPhaseOutcome and ActionStatus

by Jonathan Halliday (JIRA)

jtax subordinate TransactionImple confuses TwoPhaseOutcome and ActionStatus --------------------------------------------------------------------------- Key: JBTM-506 URL: https://jira.jboss.org/jira/browse/JBTM-506 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Jonathan Halliday Assignee: Mark Little Fix For: 4.6 In some methods of com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple, code of the form int res = subAct.doFoo(); switch(res) case ActionStatus.Bar: is found. This is incorrect, as the methods on SubordinateAtomicAction return TwoPhaseOutome not ActionStatus. In the JTA the SubordinateAtomicAction returns ActionStatus which is probably where the confusion arises, so arguably it's actually the JTAX version of SubordinateAtomicAction which is at fault, not the TransactionImple. Since the case statements will need reworking anyhow, it's probably worth looking that the way 'try to commit but actually have to rollback' is handled. In the JTA this throws RollbackException as the rollback is clean. In the JTAX it results in a HeuristicRollback due to the way the states and exceptions are mapped. This is perhaps less user friendly than it could be. -- 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, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-500) InputObjectState cannot handle null type in copy constructor

by Mark Little (JIRA)

InputObjectState cannot handle null type in copy constructor ------------------------------------------------------------ Key: JBTM-500 URL: https://jira.jboss.org/jira/browse/JBTM-500 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Priority: Minor Fix For: 4.6 Not a problem since all places we create InputObjectStates have assigned types but just in case ... -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-504) JTS JCA 1PC should call 1PC on transaction

by Mark Little (JIRA)

JTS JCA 1PC should call 1PC on transaction ------------------------------------------ Key: JBTM-504 URL: https://jira.jboss.org/jira/browse/JBTM-504 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 Currently it calls prepare and then commit or rollback on the underlying transaction. There is a one-phase commit method on the underlying transaction that it should call instead. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-502) XTS code is relying upon JBowssWS Native W3CEndpointReference feature which disappears in JBossWS 3.1.0

by Andrew Dinn (JIRA)

XTS code is relying upon JBowssWS Native W3CEndpointReference feature which disappears in JBossWS 3.1.0 -------------------------------------------------------------------------------------------------------- Key: JBTM-502 URL: https://jira.jboss.org/jira/browse/JBTM-502 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 Fix For: 4.6 The XTS code relies upon method getAddress() of class W3CEndpointReference in the JBowssWS Native stack implementation. This method has been removed in JBowssWS Native 3.1.0 because the implemenation does not pass the TCK tests if it is included. So, the XTS code needs to identify another means of obtaining the address wrapped up inside a W3CEndpointReference. -- 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, 9 months

1
2
0 / 0

← Newer
1
...
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2009