May 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2670?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2670: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update raw-xts-api-demo quickstart > ---------------------------------- > > Key: JBTM-2670 > URL: https://issues.jboss.org/browse/JBTM-2670 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2670?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Gytis Trikleris created pull request #165 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Update raw-xts-api-demo quickstart > ---------------------------------- > > Key: JBTM-2670 > URL: https://issues.jboss.org/browse/JBTM-2670 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2673) ThreadUtil getThreadId(Thread) ignores argument

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2673?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2673: ------------------------------------- Analysis shows that our usage of this internally (that doesn't use Thread.currentThread() as the argument) is: 1. BasicAction::addChildThread(Thread) which is a public method but is unused by ourselves 2. BasicAction::removeAllChildThreads - this is called by the reaper but because typical usage is via JTA which requires the app thread to disassociate we have not had reports on this > ThreadUtil getThreadId(Thread) ignores argument > ----------------------------------------------- > > Key: JBTM-2673 > URL: https://issues.jboss.org/browse/JBTM-2673 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > During investigation of https://developer.jboss.org/thread/269784?start=15&tstart=0 it was observed that the ThreadUtil implementation does not use the Thread argument and simply uses a ThreadLocal: > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2673) ThreadUtil getThreadId(Thread) ignores argument

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2673: ----------------------------------- Summary: ThreadUtil getThreadId(Thread) ignores argument Key: JBTM-2673 URL: https://issues.jboss.org/browse/JBTM-2673 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next During investigation of https://developer.jboss.org/thread/269784?start=15&tstart=0 it was observed that the ThreadUtil implementation does not use the Thread argument and simply uses a ThreadLocal: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2670) Update raw-xts-api-demo quickstart

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2670?page=com.atlassian.jira.plugin.... ] Work on JBTM-2670 started by Gytis Trikleris. --------------------------------------------- > Update raw-xts-api-demo quickstart > ---------------------------------- > > Key: JBTM-2670 > URL: https://issues.jboss.org/browse/JBTM-2670 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > raw-xts-api-demo quickstart has out of date readme and dependencies. It doesn't work with current WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2583: --------------------------------- > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.17.Final, 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: (was: 5.2.17.Final) > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2583. ------------------------------- Resolution: Done > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2583: --------------------------------- > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: 5.2.17.Final > Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.17.Final, 5.3.0.Final > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 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 May 2016