September 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2229) Issue with issue recovering AA with CMR, recovers OK but via orphan detection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2229?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2229: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1124861|https://bugzilla.redhat.com/show_bug.cgi?id=1124861] from MODIFIED to ON_QA > Issue with issue recovering AA with CMR, recovers OK but via orphan detection > ----------------------------------------------------------------------------- > > Key: JBTM-2229 > URL: https://issues.jboss.org/browse/JBTM-2229 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.21, 5.0.2 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.22, 5.0.3 > > > The issue is with the CMR recovery module when it needs to update the underlying AA to modify it with the correct value from the CMR XIDS table. > If this AA does not have Serializable XARs, it will lead to the Xid being removed from XARM during getNewXAResource (via restore_state of the XARR). When the later AARM tries to recover the AA, it means a corresponding XAR for the XID cannot be located in the XARM by the XARR and an error message is reported. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1341) Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1341?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1341. ------------------------------- Resolution: Done > Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1341 > URL: https://issues.jboss.org/browse/JBTM-1341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 4.17.23, 5.0.0.M2 > > > It is too easy to miss the warning message. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2255) Do not return StatusCommiting, if transaction was commited by the original transaction manager

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2255?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2255: ---------------------------------- Description: We need to check if the transaction is really in flight before returning status as committing. Previously code assumed, that if returned status is StatusCommitted, the only reason why the resource invoked replay_completion is that the transaction is in the process of committing. However, as shown by the attached bugzilla, another work flow is also possible. Because Oracle database returned XAException.XAER_RMFAIL, second resource was committed successfully and the client was told that the transaction committed successfully. Recovery was left to sort out the issue with the database. Once the database resource invoked replay_completion and transaction manager saw the status of the transaction as StatusCommitted, it assumed that it is still in action even though there is no BasicAction available. was: We need to check if the transaction is really in flight before returning status as committing. Previously code assumed, that if returned status is StatusCommitted, the only reason why the resource invoked replay_completion is that the transaction is in the process of committing. However, as shown by the attached bugzilla, following work flow is still possible: > Do not return StatusCommiting, if transaction was commited by the original transaction manager > ---------------------------------------------------------------------------------------------- > > Key: JBTM-2255 > URL: https://issues.jboss.org/browse/JBTM-2255 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.23 > > > We need to check if the transaction is really in flight before returning status as committing. Previously code assumed, that if returned status is StatusCommitted, the only reason why the resource invoked replay_completion is that the transaction is in the process of committing. > However, as shown by the attached bugzilla, another work flow is also possible. Because Oracle database returned XAException.XAER_RMFAIL, second resource was committed successfully and the client was told that the transaction committed successfully. Recovery was left to sort out the issue with the database. Once the database resource invoked replay_completion and transaction manager saw the status of the transaction as StatusCommitted, it assumed that it is still in action even though there is no BasicAction available. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2255) Do not return StatusCommiting, if transaction was commited by the original transaction manager

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2255?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2255: ---------------------------------- Description: We need to check if the transaction is really in flight before returning status as committing. Previously code assumed, that if returned status is StatusCommitted, the only reason why the resource invoked replay_completion is that the transaction is in the process of committing. However, as shown by the attached bugzilla, following work flow is still possible: > Do not return StatusCommiting, if transaction was commited by the original transaction manager > ---------------------------------------------------------------------------------------------- > > Key: JBTM-2255 > URL: https://issues.jboss.org/browse/JBTM-2255 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.23 > > > We need to check if the transaction is really in flight before returning status as committing. Previously code assumed, that if returned status is StatusCommitted, the only reason why the resource invoked replay_completion is that the transaction is in the process of committing. > However, as shown by the attached bugzilla, following work flow is still possible: -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2255) Do not return StatusCommiting, if transaction was commited by the original transaction manager

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2255?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2255: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/727 > Do not return StatusCommiting, if transaction was commited by the original transaction manager > ---------------------------------------------------------------------------------------------- > > Key: JBTM-2255 > URL: https://issues.jboss.org/browse/JBTM-2255 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.23 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2255) Do not return StatusCommiting, if transaction was commited by the original transaction manager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2255?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-2255: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1080035 > Do not return StatusCommiting, if transaction was commited by the original transaction manager > ---------------------------------------------------------------------------------------------- > > Key: JBTM-2255 > URL: https://issues.jboss.org/browse/JBTM-2255 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.23 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2255) Do not return StatusCommiting, if transaction was commited by the original transaction manager

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2255: ------------------------------------- Summary: Do not return StatusCommiting, if transaction was commited by the original transaction manager Key: JBTM-2255 URL: https://issues.jboss.org/browse/JBTM-2255 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 4.17.23 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2251) Replace killall with pkill in the CI build script

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2251?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2251: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Replace killall with pkill in the CI build script > ------------------------------------------------- > > Key: JBTM-2251 > URL: https://issues.jboss.org/browse/JBTM-2251 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > Some of our CI machines are missing killall which is non-standard. Replace it with pkill. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1341) Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1341?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-1341: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1139102 > Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1341 > URL: https://issues.jboss.org/browse/JBTM-1341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 4.17.23, 5.0.0.M2 > > > It is too easy to miss the warning message. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1341) Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1341?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1341: -------------------------------- Fix Version/s: 4.17.23 > Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1341 > URL: https://issues.jboss.org/browse/JBTM-1341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 4.17.23, 5.0.0.M2 > > > It is too easy to miss the warning message. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 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 September 2014