August 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1469) Move TXBridge quickstart into JDF

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1469?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1469. ------------------------------- Fix Version/s: (was: 6.later) Resolution: Won't Fix May reconsider it for later > Move TXBridge quickstart into JDF > --------------------------------- > > Key: JBTM-1469 > URL: https://issues.jboss.org/browse/JBTM-1469 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, TxBridge, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > TXBridge is now supported, so we can move one or more of the quickstarts across to JDF. We should first run this by Pete and get a JDF Jira created, then link this one through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1922) RTS error and warning messages do have unique codes for identification purposes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1922?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1922: -------------------------------- Issue Type: Bug (was: Task) > RTS error and warning messages do have unique codes for identification purposes > ------------------------------------------------------------------------------- > > Key: JBTM-1922 > URL: https://issues.jboss.org/browse/JBTM-1922 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.0.0.M4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > Original Estimate: 2 days > Remaining Estimate: 2 days > > ANDIAMO-7 says that all error and warning messages should have a unique code that can be used to identify them. RTS does not conform with this requirement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2481: -------------------------------- Priority: Minor (was: Major) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2481: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2329) Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2329?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2329: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Add a management API that an AbstractRecord provider can implement to clear the heuristic state of a transaction > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2329 > URL: https://issues.jboss.org/browse/JBTM-2329 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.later > > > If an AbstractRecord type has resulted in a heuristic state, it would be useful to provide some form of management API to clear the state on the resource manager. > After discussion on the forum, it seems likely the API would be something like: > Update AbstractRecord to change the return type of value() to the HeuristicManagement interface (rather than Object). Although value() is maybe not the most accurate term and it does appear that this is used internally by XAResourceRecord in an unintended manner (i.e. not dealing with HeuristicInformation. > Add a new interface of modify the existing HeuristicInformation (the current version of which is to be deprecated in: JBTM-2328) > {code} > public interface HeuristicManagement > { > public void resolve() throws CouldNotResolveException; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2151) Create a Quickstart showing MongoDB and Compensations API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2151?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2151: -------------------------------- Issue Type: Task (was: Feature Request) > Create a Quickstart showing MongoDB and Compensations API > --------------------------------------------------------- > > Key: JBTM-2151 > URL: https://issues.jboss.org/browse/JBTM-2151 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations, Demonstrator > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1107: -------------------------------- Issue Type: Enhancement (was: Task) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Compensations > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers would be invoked in case of the system crash. > In addition, @CompensationScoped beans should be available during the recovery. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2124: -------------------------------- Fix Version/s: 5.later > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondřej Chaloupka > Assignee: Gytis Trikleris > Fix For: 5.later > > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2116) SPI: Unique identifier for a transaction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2116?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2116: -------------------------------- Fix Version/s: 5.later > SPI: Unique identifier for a transaction > ---------------------------------------- > > Key: JBTM-2116 > URL: https://issues.jboss.org/browse/JBTM-2116 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Fix For: 5.later > > > The Narayana SPI should provide a method that returns a unique identifier for a transaction that is stable for its entire lifecycle. > {noformat} > public Object getIdentifier(Transaction tx) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2103) ORB-less JTS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2103?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2103: -------------------------------- Fix Version/s: 5.later > ORB-less JTS > ------------ > > Key: JBTM-2103 > URL: https://issues.jboss.org/browse/JBTM-2103 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.0.0 > Reporter: Mark Little > Assignee: Michael Musgrove > Fix For: 5.later > > > At some point in the future there's a good chance that the ORB requirement will be removed from EE entirely. If that happens we need to be able to react and ensure that the JTS continues to work because it’s the most complete distributed transaction implementation that we possess. Now there are two ways to do that: > (i) we ship our own ORB, either JacORB or something else, say. > (ii) we remove the dependency on CORBA entirely. > Whilst (i) is a good short term option, I think we need to look at (ii). An old in-house TM that JBoss had which Narayana replaced had a JTS implementation which supported CORBA and JBoss Remoting (I think it was Remoting). Ultimately what we need is a high performance distributed transactions implementation and JTS is it today but it has a dependency on CORBA that we need to try to remove and yet keep most of the non-ORB generated code/dependencies. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2015