June 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2911) Allow BasicXARecovery to be rescanned by periodic recovery

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2911?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2911: -------------------------------- Component/s: Transactional Driver > Allow BasicXARecovery to be rescanned by periodic recovery > ---------------------------------------------------------- > > Key: JBTM-2911 > URL: https://issues.jboss.org/browse/JBTM-2911 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transactional Driver > Reporter: Tom Jenkinson > Fix For: 5.next > > > Currently BasicXARecovery will only return it's configured XAResources for the first periodic recovery scan. It would be useful to allow it to return the same set in subsequent executions of periodic recovery. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2910) Don't allow transactional driver recovery handler to close underlying JDBC connection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2910?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2910: -------------------------------- Component/s: Transactional Driver > Don't allow transactional driver recovery handler to close underlying JDBC connection > ------------------------------------------------------------------------------------- > > Key: JBTM-2910 > URL: https://issues.jboss.org/browse/JBTM-2910 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > As the reference to the JDBC2RecoveryConnection is not retained, it is eligible for garbage collection. It's finalizer calls the connection close and can prevent recovery from completing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2909) Use interposed sync for Transactional Driver close connection call

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2909?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2909: -------------------------------- Component/s: Transactional Driver > Use interposed sync for Transactional Driver close connection call > ------------------------------------------------------------------ > > Key: JBTM-2909 > URL: https://issues.jboss.org/browse/JBTM-2909 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > HHH registers as an interposed sync so we need to so we can close after it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2905) JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2905?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2905: ------------------------------------- I will revert it from 5.5.25 as there is no JBEAP. > JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2905 > URL: https://issues.jboss.org/browse/JBTM-2905 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > The class {{JCAServerTransactionHeaderReader}} is placed under package {{com.hp.mwtests.ts.jta.jts.tools.}} which means is not available during runtime of tooling. As the header reader is used by {{com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser}} it brings situations where the record can't be loaded by tooling. The browser seems to be used by Expiry Scanner and that suffers by that fact. > The WFLY start sequence contains info of not possible to load the reader when the object store contains some unfinished jca subordinate transaction. > {code} > INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @6b419da (finder: local module finder @3b2da18f (roots: /home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules/system/layers/base,/home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules))] > {code} > The point is to move the jca reader under jts tooling package to be compiled and distributed in the {{jts}} jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2905) JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2905?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2905: -------------------------------- Fix Version/s: (was: 5.2.25.Final) > JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2905 > URL: https://issues.jboss.org/browse/JBTM-2905 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > The class {{JCAServerTransactionHeaderReader}} is placed under package {{com.hp.mwtests.ts.jta.jts.tools.}} which means is not available during runtime of tooling. As the header reader is used by {{com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser}} it brings situations where the record can't be loaded by tooling. The browser seems to be used by Expiry Scanner and that suffers by that fact. > The WFLY start sequence contains info of not possible to load the reader when the object store contains some unfinished jca subordinate transaction. > {code} > INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @6b419da (finder: local module finder @3b2da18f (roots: /home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules/system/layers/base,/home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules))] > {code} > The point is to move the jca reader under jts tooling package to be compiled and distributed in the {{jts}} jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2908) JCA committed inflow transaction is not moved to assumed completed category for JTS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2908?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2908: -------------------------------- Fix Version/s: 5.2.25.Final > JCA committed inflow transaction is not moved to assumed completed category for JTS > ----------------------------------------------------------------------------------- > > Key: JBTM-2908 > URL: https://issues.jboss.org/browse/JBTM-2908 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.6.1.Final, 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.2.25.Final, 5.next > > > We have test which checks whether EIS is capable to finish transaction after JVM crash. > The scenario is following: > - 2 test XA resources are enlisted > - EIS RAR XATerminator calls prepare and commit > - JVM crash occurs at the start of the first XAResource.commit call > - app server is restarted > - doRecoveryScan()/waitForOrphanInterval/doRecoveryScan() > - both (mock) XAResources are not rolled-back > - EIS XATerminator.commit is called > - doRecoveryScan()/waitForOrphanInterval/doRecoveryScan() > - both (mock) XAResources are committed > but the committed tx is not removed from log: > {code} > jvmCrashAfterPrepareJTS(org.jboss.as.test.jbossts.crashrec.jca.test.JcaInflowTransactionTestCase) Time elapsed: 125.532 sec <<< FAILURE! > java.lang.AssertionError: After commiting txn there should be no one in the txn log expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.jboss.as.test.jbossts.crashrec.jca.test.JcaInflowTransactionTestCase.jvmCrashAfterPrepareJTS(JcaInflowTransactionTestCase.java:763) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2908) JCA committed inflow transaction is not moved to assumed completed category for JTS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2908?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2908: -------------------------------- Fix Version/s: 5.next > JCA committed inflow transaction is not moved to assumed completed category for JTS > ----------------------------------------------------------------------------------- > > Key: JBTM-2908 > URL: https://issues.jboss.org/browse/JBTM-2908 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.6.1.Final, 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.next > > > We have test which checks whether EIS is capable to finish transaction after JVM crash. > The scenario is following: > - 2 test XA resources are enlisted > - EIS RAR XATerminator calls prepare and commit > - JVM crash occurs at the start of the first XAResource.commit call > - app server is restarted > - doRecoveryScan()/waitForOrphanInterval/doRecoveryScan() > - both (mock) XAResources are not rolled-back > - EIS XATerminator.commit is called > - doRecoveryScan()/waitForOrphanInterval/doRecoveryScan() > - both (mock) XAResources are committed > but the committed tx is not removed from log: > {code} > jvmCrashAfterPrepareJTS(org.jboss.as.test.jbossts.crashrec.jca.test.JcaInflowTransactionTestCase) Time elapsed: 125.532 sec <<< FAILURE! > java.lang.AssertionError: After commiting txn there should be no one in the txn log expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.jboss.as.test.jbossts.crashrec.jca.test.JcaInflowTransactionTestCase.jvmCrashAfterPrepareJTS(JcaInflowTransactionTestCase.java:763) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2905) JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2905?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2905. --------------------------------- Resolution: Done > JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2905 > URL: https://issues.jboss.org/browse/JBTM-2905 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.2.25.Final, 5.next > > > The class {{JCAServerTransactionHeaderReader}} is placed under package {{com.hp.mwtests.ts.jta.jts.tools.}} which means is not available during runtime of tooling. As the header reader is used by {{com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser}} it brings situations where the record can't be loaded by tooling. The browser seems to be used by Expiry Scanner and that suffers by that fact. > The WFLY start sequence contains info of not possible to load the reader when the object store contains some unfinished jca subordinate transaction. > {code} > INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @6b419da (finder: local module finder @3b2da18f (roots: /home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules/system/layers/base,/home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules))] > {code} > The point is to move the jca reader under jts tooling package to be compiled and distributed in the {{jts}} jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2911) Allow BasicXARecovery to be rescanned by periodic recovery

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2911: ----------------------------------- Summary: Allow BasicXARecovery to be rescanned by periodic recovery Key: JBTM-2911 URL: https://issues.jboss.org/browse/JBTM-2911 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Tom Jenkinson Currently BasicXARecovery will only return it's configured XAResources for the first periodic recovery scan. It would be useful to allow it to return the same set in subsequent executions of periodic recovery. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2910) Don't allow transactional driver recovery handler to close underlying JDBC connection

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2910?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2910: -------------------------------- Description: As the reference to the JDBC2RecoveryConnection is not retained, it is eligible for garbage collection. It's finalizer calls the connection close and can prevent recovery from completing. (was: As the reference to the JDBC2RecoveryConnection is not retained, it is eligible for garbage collection. It's finalizer calls the connection close and prevents recovery from completing.) > Don't allow transactional driver recovery handler to close underlying JDBC connection > ------------------------------------------------------------------------------------- > > Key: JBTM-2910 > URL: https://issues.jboss.org/browse/JBTM-2910 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > As the reference to the JDBC2RecoveryConnection is not retained, it is eligible for garbage collection. It's finalizer calls the connection close and can prevent recovery from completing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2017