December 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2955) Add a filter that checks for running subordinate transactions before identifying a branch as orphaned

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2955?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2955: -------------------------------- Priority: Critical (was: Major) > Add a filter that checks for running subordinate transactions before identifying a branch as orphaned > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2955 > URL: https://issues.jboss.org/browse/JBTM-2955 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.next > > > It is possible that when a transaction is propagated to another JVM using EJB remoting (which uses the SubordinationManager for importing a TX) and it is slow to prepare orphan detection may rollback one of its previously prepared XAResources. > We can detect if a subordinate TX is already running for a gtrid so we can use that. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2974) Ensure that we only recover subordinate orphan Xids for servers that this server is configured for

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2974?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2974: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Ensure that we only recover subordinate orphan Xids for servers that this server is configured for > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2974 > URL: https://issues.jboss.org/browse/JBTM-2974 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > There are two filters where we filter for subordinates but one does not check if the server is in the list of recovery nodes and one just checks to see if it matches the local server. Neither check is correct and we should see if it is in the list of XA recovery nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2972) Add connection pooling facilities to transactionaldriver such that it will allow close to return the connection to the pool

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2972?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2972: -------------------------------- Fix Version/s: 5.next > Add connection pooling facilities to transactionaldriver such that it will allow close to return the connection to the pool > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2972 > URL: https://issues.jboss.org/browse/JBTM-2972 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Tom Jenkinson > Fix For: 5.next > > > Currently the connection is pooled in that that the same connection is returned during a TX. We would like to return the connection to the pool so that it can be reused. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2974) Ensure that we only recover subordinate orphan Xids for servers that this server is configured for

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2974?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2974: -------------------------------- Priority: Blocker (was: Critical) > Ensure that we only recover subordinate orphan Xids for servers that this server is configured for > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2974 > URL: https://issues.jboss.org/browse/JBTM-2974 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > There are two filters where we filter for subordinates but one does not check if the server is in the list of recovery nodes and one just checks to see if it matches the local server. Neither check is correct and we should see if it is in the list of XA recovery nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2974) Ensure that we only recover subordinate orphan Xids for servers that this server is configured for

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2974?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2974: -------------------------------- Fix Version/s: 5.next 5.2.next 5.5.next > Ensure that we only recover subordinate orphan Xids for servers that this server is configured for > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2974 > URL: https://issues.jboss.org/browse/JBTM-2974 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > There are two filters where we filter for subordinates but one does not check if the server is in the list of recovery nodes and one just checks to see if it matches the local server. Neither check is correct and we should see if it is in the list of XA recovery nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2974) Ensure that we only recover subordinate orphan Xids for servers that this server is configured for

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2974?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2974: -------------------------------- Fix Version/s: (was: 5.2.next) (was: 5.5.next) > Ensure that we only recover subordinate orphan Xids for servers that this server is configured for > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2974 > URL: https://issues.jboss.org/browse/JBTM-2974 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > There are two filters where we filter for subordinates but one does not check if the server is in the list of recovery nodes and one just checks to see if it matches the local server. Neither check is correct and we should see if it is in the list of XA recovery nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2975) Ensure that we only recover subordinate orphan Xids for servers that this server is configured for

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2975: ----------------------------------- Summary: Ensure that we only recover subordinate orphan Xids for servers that this server is configured for Key: JBTM-2975 URL: https://issues.jboss.org/browse/JBTM-2975 Project: JBoss Transaction Manager Issue Type: Bug Components: Recovery Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Critical There are two filters where we filter for subordinates but one does not check if the server is in the list of recovery nodes and one just checks to see if it matches the local server. Neither check is correct and we should see if it is in the list of XA recovery nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2974) Ensure that we only recover subordinate orphan Xids for servers that this server is configured for

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2974?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1265 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Ensure that we only recover subordinate orphan Xids for servers that this server is configured for > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2974 > URL: https://issues.jboss.org/browse/JBTM-2974 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > > There are two filters where we filter for subordinates but one does not check if the server is in the list of recovery nodes and one just checks to see if it matches the local server. Neither check is correct and we should see if it is in the list of XA recovery nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2974) Ensure that we only recover subordinate orphan Xids for servers that this server is configured for

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2974: ----------------------------------- Summary: Ensure that we only recover subordinate orphan Xids for servers that this server is configured for Key: JBTM-2974 URL: https://issues.jboss.org/browse/JBTM-2974 Project: JBoss Transaction Manager Issue Type: Bug Components: Recovery Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Critical There are two filters where we filter for subordinates but one does not check if the server is in the list of recovery nodes and one just checks to see if it matches the local server. Neither check is correct and we should see if it is in the list of XA recovery nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2955) Add a filter that checks for running subordinate transactions before identifying a branch as orphaned

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2955?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2955: -------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1246 > Add a filter that checks for running subordinate transactions before identifying a branch as orphaned > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2955 > URL: https://issues.jboss.org/browse/JBTM-2955 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It is possible that when a transaction is propagated to another JVM using EJB remoting (which uses the SubordinationManager for importing a TX) and it is slow to prepare orphan detection may rollback one of its previously prepared XAResources. > We can detect if a subordinate TX is already running for a gtrid so we can use that. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 December 2017