November 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-932) Recover inflight subordinate transactions

by Tom Jenkinson (Created) (JIRA)

Recover inflight subordinate transactions ----------------------------------------- Key: JBTM-932 URL: https://issues.jboss.org/browse/JBTM-932 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Fix For: 4.15.4 The call to XATerminator::recover() only returns transactions that are in the RecoveryStore. What if? 1. EIS propagates transaction "XYZ" 2. EIS crashes 3. We are not notified of this 4. EIS recovers 5. EIS calls XATerminator::recover 6. The inflight "XYZ" is not returned as it was not prepared and is therefore not in the RecoveryStore -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

6
7
0 / 0

[JBoss JIRA] (JBTM-988) Support multiple @ServiceRequest calls per transaction

by Paul Robinson (Created) (JIRA)

Support multiple @ServiceRequest calls per transaction ------------------------------------------------------ Key: JBTM-988 URL: https://issues.jboss.org/browse/JBTM-988 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 For example, with WS-BA: {code} @ServiceRequest pubic void addToBasket(...) { ... { @Completes public void checkout() ( ... } @Compensate public void removeFromBasket(...) { ... } {code} Here addToBasket() can be called multiple times within the same transaction. If the transaction is compensated, 'removeFromBasket' is invoked once per call to 'addToBasket' and once when checkout is called. A participant is registered for every call to a method annotated with @ServiceRequest. Similar functionality should be provided for WS-AT services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
4
0 / 0

[JBoss JIRA] (JBTM-975) Allow many ServiceRequest methods to have a single set of Lifecycle methods

by Paul Robinson (Created) (JIRA)

Allow many ServiceRequest methods to have a single set of Lifecycle methods ---------------------------------------------------------------------------- Key: JBTM-975 URL: https://issues.jboss.org/browse/JBTM-975 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 By setting the 'single' attribute on a Lifecycle Handler Annotation (such as @Prepare or @Compensate) identifies whether more than one callback can be registered for the lifecycle method in response to multiple invocations of the ServiceRequest method. If it is true then the lifecycle method will be called once to the ServiceRequest method. If it is false then the lifecycle method will be called once in response to each (non-read only) call to the ServiceRequest method. The default is 'false'. Annotation: {code} @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.METHOD) public @interface Compensate { public boolean single() default false; } {code} Example: {code} @ServiceRequest public void addToBasket() { //Add another item to the basket. } @Compensate(single=true) public void emptyBasket() { //Empty every item from the basket } {code} In this example the @ServiceRequest may be invoked many times to add many items to the basket. The @Compensate method is only needed to be invoked once as the basket can be emptied in one operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
6
0 / 0

[JBoss JIRA] (JBTM-983) Ensure DataManagement values are available for all lifecycle methods

by Paul Robinson (Created) (JIRA)

Ensure DataManagement values are available for all lifecycle methods -------------------------------------------------------------------- Key: JBTM-983 URL: https://issues.jboss.org/browse/JBTM-983 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
3
0 / 0

[JBoss JIRA] (JBTM-927) Prepare on a TransactionReaper rolled back subordinate transaction returns PREPARE_READONLY rather than PREPARE_NOTOK

by Tom Jenkinson (Created) (JIRA)

Prepare on a TransactionReaper rolled back subordinate transaction returns PREPARE_READONLY rather than PREPARE_NOTOK --------------------------------------------------------------------------------------------------------------------- Key: JBTM-927 URL: https://issues.jboss.org/browse/JBTM-927 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.15.3 Reporter: Tom Jenkinson Fix For: 4.15.4, 5.0.0.M2 com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.SubordinateAtomicAction.doPrepare does not check if the state of the transaction is ABORTED -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
5
0 / 0

[JBoss JIRA] (JBTM-917) Create a XAResourceOrphanFilter to recover subordinate transactions

by Tom Jenkinson (Created) (JIRA)

Create a XAResourceOrphanFilter to recover subordinate transactions ------------------------------------------------------------------- Key: JBTM-917 URL: https://issues.jboss.org/browse/JBTM-917 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
4
0 / 0

[JBoss JIRA] (JBTM-916) Convert XID to support encoding the node name in the branch qualifier for subordinate transactions and include the parent node name in the bqual also to assist with recovery

by Tom Jenkinson (Created) (JIRA)

Convert XID to support encoding the node name in the branch qualifier for subordinate transactions and include the parent node name in the bqual also to assist with recovery ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-916 URL: https://issues.jboss.org/browse/JBTM-916 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-909) Add an API hook for deferred afterCompletion

by David Lloyd (JIRA)

Add an API hook for deferred afterCompletion -------------------------------------------- Key: JBTM-909 URL: https://issues.jboss.org/browse/JBTM-909 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: Tom Jenkinson Fix For: 4.15.x Provide an API for deferring afterCompletion callback. This comes in two parts: # A flag to pass to the commit method indicating that afterCompletion should be deferred # A separate method indicating that afterCompletion callbacks should proceed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
5
0 / 0

[JBoss JIRA] (JBTM-933) Compress the EIS name in the bqual

by Tom Jenkinson (Created) (JIRA)

Compress the EIS name in the bqual ---------------------------------- Key: JBTM-933 URL: https://issues.jboss.org/browse/JBTM-933 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Fix For: 4.15.4 Current most of the bqual is consumed by the EIS name (stored uncompressed) leaving little space for future enhancements. This was OK before, but there is potentially a requirement to use some of the bqual to store a node identifier (which, in the gtrid is able to be 36 bytes long). Jonathan has pointed out that we can maintain a file somewhere where the user passes us an EIS name of say "foo" and we can add this to the file as integer 1, and so on. This file can be reloaded at startup into a hashmap so that we can still print out the real EIS name even though the XID bqual would only consume 4 bytes now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
6
0 / 0

[JBoss JIRA] (JBTM-967) MBeans corresponding to XA resource log records do not expose the Jndi name of datasources

by Michael Musgrove (Created) (JIRA)

MBeans corresponding to XA resource log records do not expose the Jndi name of datasources ------------------------------------------------------------------------------------------ Key: JBTM-967 URL: https://issues.jboss.org/browse/JBTM-967 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.15.3 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.15.4 XA resource records now encode the Jndi name of datasources. This information needs to be reflected in the MBeans that represent these records. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 November 2011