May 2016 - jbossts-issues - Jboss List Archives

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1107: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > 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.next > > > 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.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1329142|https://bugzilla.redhat.com/show_bug.cgi?id=1329142] from NEW to ASSIGNED > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 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 updated JBTM-2675: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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.next > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2668?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Gytis Trikleris created pull request #166 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Entity manager does not join transaction properly in JTA and Hibernate quickstart > --------------------------------------------------------------------------------- > > Key: JBTM-2668 > URL: https://issues.jboss.org/browse/JBTM-2668 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2676) Allow TransactionalDriver connection.close() in afterCompletion

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2676?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2676: -------------------------------- Summary: Allow TransactionalDriver connection.close() in afterCompletion (was: Hibernate tries to close connection in afterCompletion but TransactionDriver does not allow that) > Allow TransactionalDriver connection.close() in afterCompletion > --------------------------------------------------------------- > > Key: JBTM-2676 > URL: https://issues.jboss.org/browse/JBTM-2676 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. > See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2676) Hibernate tries to close connection in afterCompletion but TransactionDriver does not allow that

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2676: ------------------------------------- Summary: Hibernate tries to close connection in afterCompletion but TransactionDriver does not allow that Key: JBTM-2676 URL: https://issues.jboss.org/browse/JBTM-2676 Project: JBoss Transaction Manager Issue Type: Bug Components: Transactional Driver Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Hibernate closes connections in afterCompletion. However, TransactionalDriver requires transaction to be in an active state in order to delist resource. See new JTA and Hibernate standalone quickstart for reproduction. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2675: -------------------------------- Fix Version/s: (was: 5.2.18.Final) > 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.next > > > 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, 11 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 updated JBTM-2675: ---------------------------------- Fix Version/s: (was: 4.17.34) > 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.2.18.Final, 5.next > > > 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, 11 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2675: -------------------------------- Fix Version/s: 5.2.18.Final > 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: 4.17.34, 5.2.18.Final, 5.next > > > 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, 11 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 updated JBTM-2675: ---------------------------------- Fix Version/s: 5.next > 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: 4.17.34, 5.next > > > 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, 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