February 2009 - jbossts-issues - Jboss List Archives

[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-497) JTS-JTA resume throws exception when resuming terminated transaction

by Mark Little (JIRA)

JTS-JTA resume throws exception when resuming terminated transaction -------------------------------------------------------------------- Key: JBTM-497 URL: https://jira.jboss.org/jira/browse/JBTM-497 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 Local JTA and JTS allow this (it's allowed in the OTS). Change for consistency. -- 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-412) Socket process id binds to the wrong interface

by Michael Musgrove (JIRA)

Socket process id binds to the wrong interface ---------------------------------------------- Key: JBTM-412 URL: https://jira.jboss.org/jira/browse/JBTM-412 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.4.0.GA, 4.4.CR2, 4.4.CR1, 4.5 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.5 If working offline, i.e. no eth0/network, and jboss is started on localhost then the server doesn't boot because SocketProcessId is binding to the wrong interface - InetAddress getByName(null) should be used instead of InetAddress.getLocalHost() -- 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] Created: (JBTM-409) WS-BA coordinator interposition support

by Jonathan Halliday (JIRA)

WS-BA coordinator interposition support --------------------------------------- Key: JBTM-409 URL: https://jira.jboss.org/jira/browse/JBTM-409 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4.0.GA Reporter: Jonathan Halliday Assignee: Andrew Dinn Fix For: 4.5 -- 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

3
10
0 / 0

[JBoss JIRA] Created: (JBTM-495) Provide handler to automate installation of subordinate transaction context when web service is invoked

by Andrew Dinn (JIRA)

Provide handler to automate installation of subordinate transaction context when web service is invoked ------------------------------------------------------------------------------------------------------- Key: JBTM-495 URL: https://jira.jboss.org/jira/browse/JBTM-495 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 If a transactional web service needs to execute in the context of its own subordinate AT transaction then it should be possible to configure a message handler on the server side to achieve this. For an incoming message the handler should check for an AT context flowed from the web client, create a subordinate AT transaction and install the subordinate context on the web service thread. It should suspend the transaction for an outgoing message. -- 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-491) WS-AT needs ot provide an API allowing a Subordinate Transaction to be created and managed from within an AT transaction.

by Andrew Dinn (JIRA)

WS-AT needs ot provide an API allowing a Subordinate Transaction to be created and managed from within an AT transaction. ------------------------------------------------------------------------------------------------------------------------- Key: JBTM-491 URL: https://jira.jboss.org/jira/browse/JBTM-491 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 A web service executing within a WS-AT transaction may wish to interpose a subordinate coordinator between itself and its own coordinator. To do so it needs to be able to start a subordinate WS-AT transaction. The current API for creating AT transactions requires calling UserTransactionFactory.userTransaction() to obtain an instance of UserTransaction and then calling begin() (or begin(final int timeout)) on the returned UserTransaction to start the transaction. If this is done within an existing AT transaction a WrongStateException is thrown. This request proposes to add the following methods to UserTransaction() public void beginSubordinate() throws WrongStateException, SystemException; public void beginSubordinate(int timeout) throws WrongStateException, SystemException; These methods will begin a subordinate transaction so long as the thread is currently associated with a WS-AT transaction. WrongStateException will be thrown if the thread is not currently associated with a WS-AT transaction. SystemException will be thrown if a problem occurs starting the transaction (this can occur for much the same reasons it can occur with the normal begin methods). -- 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
4
0 / 0

[JBoss JIRA] Created: (JBTM-494) topLevelCommit should throw HeuristicHazard on NOTA

by Mark Little (JIRA)

topLevelCommit should throw HeuristicHazard on NOTA --------------------------------------------------- Key: JBTM-494 URL: https://jira.jboss.org/jira/browse/JBTM-494 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 Currently returns FINISH_ERROR which means recovery will kick in and periodically retry. Doesn't make sense for NOTA. -- 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-492) XAResourceRecord missing cleanup when readonly

by Jonathan Halliday (JIRA)

XAResourceRecord missing cleanup when readonly ---------------------------------------------- Key: JBTM-492 URL: https://jira.jboss.org/jira/browse/JBTM-492 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation, Resource Manager Affects Versions: 4.5 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.6 When TxControl.readonlyOptimisation == true, XAResourceRecord.topLevelPrepare needs to call removeConnection before returning readonly, as BasicAction won't call it again in phase 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

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-490) Deprecate unknown() method in BA Participant interface

by Andrew Dinn (JIRA)

Deprecate unknown() method in BA Participant interface ------------------------------------------------------ Key: JBTM-490 URL: https://jira.jboss.org/jira/browse/JBTM-490 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 BA Participant interface defines an unknown() method with the following description If the participant enquires as to the status of the transaction it was registered with and that transaction is no longer available (has rolled back) then this operation will be invoked by the coordination service. Status enquiries only occur between participant completion and subsequent close or compensate. If the response to this enquiry is an InvalidState fault then this indicates that the coordinator host has lost all record of the transaction because of a crash, in which case the correct response is to call the participant's compensate() method (this is a correct step in the presumed abort protocol). InvalidState can only be sent if the participant does not exist. If GetStatus results in a Status message notifying an unexpected coordinator state (i.e. neither Active nor Compensating nor Compensated) or leads to some other soap fault being sent in reply then the correct response is to call the participant error() method since this represents an unrecoverable protocol error. This type of error is orthogonal to the recovery status of the participant or the coordinator since it can happen before or after a crash on either side (or both sides) and, where there has been a crash, before or after the participant's status is re-established. Consequently, there is no circumstance in which it would be appropriate for unknown() to be called in place of error(). -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2009