June 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2650) Remove typo from BAControler interface and its implementations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2650?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2650. --------------------------------- > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: JBTM-2650 > URL: https://issues.jboss.org/browse/JBTM-2650 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.3.3.Final > > > Fix typos in BAControler, LocalBAControler, and RemoteBAControler names. Also variables when those classes are used also have typos. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2655) QA suite failure: TestGroup_txcore_recovery (JDBC store)

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2655?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2655. --------------------------------- > QA suite failure: TestGroup_txcore_recovery (JDBC store) > -------------------------------------------------------- > > Key: JBTM-2655 > URL: https://issues.jboss.org/browse/JBTM-2655 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.3.3.Final > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-jdbcobje... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2657) Missing narayana-osgi-jta artifact with the release profile

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2657?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2657. --------------------------------- > Missing narayana-osgi-jta artifact with the release profile > ----------------------------------------------------------- > > Key: JBTM-2657 > URL: https://issues.jboss.org/browse/JBTM-2657 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Labels: JTA, OSGI > Fix For: 5.3.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 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.... ] Gytis Trikleris closed JBTM-2670. --------------------------------- > 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.3.3.Final > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2675. --------------------------------- > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 5.3.3.Final > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2663) Upgrade to jboss-connector-api_1.7_spec 1.0.0.Final in jboss-transaction-spi

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2663?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2663. --------------------------------- > Upgrade to jboss-connector-api_1.7_spec 1.0.0.Final in jboss-transaction-spi > ---------------------------------------------------------------------------- > > Key: JBTM-2663 > URL: https://issues.jboss.org/browse/JBTM-2663 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.3.3.Final > > > It includes the JTA 1.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 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, 5.2.17.Final, 4.17.34 > > > 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 4.17.34 > 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: 4.17.34, 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 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 RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2583: ----------------------------------------------- Dmitrii Tikhomirov <dtikhomi(a)redhat.com> changed the Status of [bug 1310603|https://bugzilla.redhat.com/show_bug.cgi?id=1310603] from ASSIGNED to MODIFIED > 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2016