March 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-509) Document BA recovery API

by Andrew Dinn (JIRA)

Document BA recovery API ------------------------ Key: JBTM-509 URL: https://jira.jboss.org/jira/browse/JBTM-509 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-493) New API for creatiing suordinate AT transacctions needs to be documented

by Andrew Dinn (JIRA)

New API for creatiing suordinate AT transacctions needs to be documented ------------------------------------------------------------------------ Key: JBTM-493 URL: https://jira.jboss.org/jira/browse/JBTM-493 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.6 Need to document UserTransaction.beginSubordinate() and UserTransaction.beginSubordinate(int timeout) -- 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

[JBoss JIRA] Created: (JBTM-416) When running in a server the Recovery Manager does not reuse the servers' orb

by Michael Musgrove (JIRA)

When running in a server the Recovery Manager does not reuse the servers' orb ----------------------------------------------------------------------------- Key: JBTM-416 URL: https://jira.jboss.org/jira/browse/JBTM-416 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.4.0.GA Reporter: Michael Musgrove Assignee: Jonathan Halliday Fix For: 4.4.0.GA Start two servers on the same host but bound to different interfaces. The Recovery manager on the second server fails to start since it tries to create a new ORB on the default jacorb address (see JacOrbRCServiceInit.java) - ie it neither reuses the existing server orb nor does it bind to the jboss.bind.address. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBTM-510) WS-AT Subordinat Context Handler needs to reinstate existing subordinate if there is one

by Andrew Dinn (JIRA)

WS-AT Subordinat Context Handler needs to reinstate existing subordinate if there is one ---------------------------------------------------------------------------------------- Key: JBTM-510 URL: https://jira.jboss.org/jira/browse/JBTM-510 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.6 The WS-AT subordinate transaction context handler creates a subordinate transaction for an incoming WS-AT transaction and then resumes it, thus ensuring that the web service performs its operations in the subordinate transaction. The problem is that it needs to ensure that on subsequent invocations of the web service in the same top-level transaction it resumes the same subordinate transaction (it currently always creates a subordinate). The hard bit is also ensuring that the parent to subordinate association is garbage collected when either the parent or subordinate commits or rolls back. -- 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
2
0 / 0

[JBoss JIRA] Updated: (JBTM-221) Improve WS-T example

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-221?page=com.atlassian.jira.plugi... ] Jonathan Halliday updated JBTM-221: ----------------------------------- Fix Version/s: 4.7 (was: 4.6) > Improve WS-T example > -------------------- > > Key: JBTM-221 > URL: https://jira.jboss.org/jira/browse/JBTM-221 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, WS-T Implementation > Affects Versions: 4.2.3 > Reporter: Mark Little > Assignee: Jonathan Halliday > Fix For: 4.7 > > > It would be nice if the various windows could be displayed outside of a browser, for example. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBTM-496) make beforeCompletion sync behaviour configurable

by Jonathan Halliday (JIRA)

make beforeCompletion sync behaviour configurable ------------------------------------------------- Key: JBTM-496 URL: https://jira.jboss.org/jira/browse/JBTM-496 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration, JTA Implementation, JTS Implementation Affects Versions: 4.5 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.6 The JTA and JTS/OTS specs are ambiguous with respect to the circumstances in which beforeCompletion synchronizations should be invoked. "The Synchronization.beforeCompletion method is called prior to the start of the two-phase transaction commit process. This call is executed with the transaction context of the transaction that is being committed." "The beforeCompletion method is called by the transaction manager prior to the start of the two-phase transaction commit process. This call is executed with the transaction context of the transaction that is being committed." Interestingly the change log for the JTA spec also includes this revision: "Interface javax.transaction.Synchronization, method beforeCompletion, change the following phrase in the description "start of the transaction completion process" to "start of the two-phase transaction commit process"." which could be read as implying that beforeCompletion should not be called when a transaction is being committed via a onePhase commit optimization. However, that interpretation makes little sense and is accordingly rejected - beforeCompletions will always be run before a xa resource commit in either phase. Nevertheless, that still leaves open the question of the intended behaviour in cases such as the sequence setRollbackOnly(); commit(); In general we take the view that beforeCompletions are intended to allow cached data to be flushed to stable store and thus invoking them when it is already known the transaction cannot commit, is a waste of time. However, this is considered an optimization rather than an absolute requirement. A more extreme view appears to be taken by the EJB spec and testsuite, which expects the beforeCompletion will definitely NOT run after a setRollbackOnly, although it seems to have little basis for this assertion. To allow for this ambiguity, the behaviour of the system should be configurable. -- 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

[JBoss JIRA] Created: (JBTM-447) Implement tests for WS-AT subordinate transaction recovery

by Andrew Dinn (JIRA)

Implement tests for WS-AT subordinate transaction recovery ---------------------------------------------------------- Key: JBTM-447 URL: https://jira.jboss.org/jira/browse/JBTM-447 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-431) Implement test suite for WS-BA coordinator and participant recovery

by Andrew Dinn (JIRA)

Implement test suite for WS-BA coordinator and participant recovery ------------------------------------------------------------------- Key: JBTM-431 URL: https://jira.jboss.org/jira/browse/JBTM-431 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.6 Now that WS-BA recovery is available it needs to be tested thoroughly, preferably via an automated process. -- 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-387) Implement test suite for WS-AT coordinator and participant recovery

by Andrew Dinn (JIRA)

Implement test suite for WS-AT coordinator and participant recovery ------------------------------------------------------------------- Key: JBTM-387 URL: https://jira.jboss.org/jira/browse/JBTM-387 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.4.CR2 Reporter: Andrew Dinn Assignee: Andrew Dinn Now that WS-AT recovery is available it needs to be tested thoroughly, preferably via an automated process. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBTM-507) jtax subordinate transactions throw unnecessary heuristics

by Jonathan Halliday (JIRA)

jtax subordinate transactions throw unnecessary heuristics ---------------------------------------------------------- Key: JBTM-507 URL: https://jira.jboss.org/jira/browse/JBTM-507 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration, JTS Implementation Affects Versions: 4.5 Reporter: Jonathan Halliday Assignee: Mark Little Fix For: 4.6 The SubordinateTestCase is showing up cases where the JTAX version of subordinate transactions is throwing HeuristicCommit or HeuristicRollback in cases where this should not be necessary. For example begin() setRollbackOnly() commit() throws RollbackExcpetion in the JTA version but a heuristic in the JTAX flavour. It would be better if the behaviour was consistent between the two. -- 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
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2009