June 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2544: ----------------------------------- Assignee: (was: Tom Jenkinson) > RTS inbound bridge recovery does not work with JTS > -------------------------------------------------- > > Key: JBTM-2544 > URL: https://issues.jboss.org/browse/JBTM-2544 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Fix For: 5.later > > > If JTS is enabled, crash scenario when system fails just before the commit does not complete correctly. Instead of being committed, resource is rolled back by XARecoveryModule. > In JTA case, XARecoveryModule does not find any XAResourceRecords and bridge recovery is handled by InboundBridgeRecoveryModule. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2339: ----------------------------------- Assignee: (was: Tom Jenkinson) > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Gytis Trikleris > Fix For: 5.later > > > Investigate the feasibility of MongoDB compensations patent implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2678) @TxLogged annotation does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2678: ----------------------------------- Assignee: (was: Tom Jenkinson) > @TxLogged annotation does not work > ---------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa581... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1789) Simplify deploy plugin configuration and don't deploy uber (shaded) jars

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1789?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1789: ----------------------------------- Assignee: (was: Tom Jenkinson) > Simplify deploy plugin configuration and don't deploy uber (shaded) jars > ------------------------------------------------------------------------ > > Key: JBTM-1789 > URL: https://issues.jboss.org/browse/JBTM-1789 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Paul Gier > Fix For: 6.later > > > There is currently configuration of the maven deploy plugin in several modules to either deploy or not deploy artifacts and poms to the Maven repo. The configuration could be simplified using properties, and the uber jars (generated by the shade plugin) should not be deployed to the Maven repository. > Here is the current deployment status and proposed for the modules. > ||Module Name||Current Deployment||Proposed|| > | Narayana: all | deployed | deployed | > | Narayana: common | deployed | deployed | > | Narayana: Arjunacore | deployed | deployed | > | Narayana: ArjunaCore arjuna | deployed | deployed | > | Narayana: ArjunaCore txoj | deployed | deployed | > | Narayana: ArjunaCore arjunacore | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTA | deployed | deployed | > | Narayana: ArjunaJTA jta | deployed | deployed | > | Narayana: ArjunaJTA cdi | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA jdbc | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTA narayana-jta | deployed | {color:red} skipped {color} | > | Narayana: XTS | deployed | deployed | > | Narayana: XTS byteman_support | deployed | deployed | > | Narayana: XTS WSAS | skipped | skipped | > | Narayana: XTS WSAS xts-test-servlet | skipped | skipped | > | Narayana: XTS WS-C | skipped | skipped | > | Narayana: XTS WSCF | skipped | skipped | > | Narayana: XTS WS-T | skipped | skipped | > | Narayana: XTS WSTX | skipped | skipped | > | Narayana: XTS recovery | skipped | skipped | > | Narayana: XTS bridge | skipped | skipped | > | Narayana: XTS sar | skipped | skipped | > | Narayana: XTS jbossxts | deployed | deployed | > | Narayana: XTS localjunit | skipped | skipped | > | Narayana: XTS localjunit unit | skipped | skipped | > | Narayana: XTS WSTX11-interop | skipped | skipped | > | Narayana: XTS WSTFSC07-interop | skipped | skipped | > | Narayana: XTS localjunit xtstest | skipped | skipped | > | Narayana: XTS localjunit crash-recovery-tests | skipped | skipped | > | Narayana: ArjunaJTS | deployed | deployed | > | Narayana: ArjunaJTS idl | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS idl jacorb | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS orbportability | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jts | skipped | {color:red} deployed {color} | > | Narayana: ArjunaJTS jtax | skipped | {color:red} deployed {color} | > | Narayana: ArjuntaJTS narayana-jts-jacorb | deployed | {color:red} skipped {color} | > | Narayana: ArjunaJTS integration | deployed | deployed | > | Narayana: rest-tx | deployed | deployed | > | Narayana: rest-tx util | deployed | deployed | > | Narayana: rest-tx tx (RESTful API for Atomic Transactions) | deployed | deployed | > | Narayana: rest-tx webservice | skipped | skipped | > | Narayana: rest-tx integration | deployed | deployed | > | Narayana: txbridge | deployed | deployed | > | Narayana: fileio | deployed | deployed | > | Narayana: STM | skipped | skipped | > | Narayana: txframework | deployed | deployed | > | Narayana: narayana-full | skipped | skipped | > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2854) XATerminatorImple.importTransaction can produce ArrayIndexOutOfBoundsException

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2854?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2854: ----------------------------------- Assignee: (was: Tom Jenkinson) > XATerminatorImple.importTransaction can produce ArrayIndexOutOfBoundsException > ------------------------------------------------------------------------------ > > Key: JBTM-2854 > URL: https://issues.jboss.org/browse/JBTM-2854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: David Lloyd > > Here is what the stack trace looks like: > {noformat} > Caused by: Remote exception java.lang.ArrayIndexOutOfBoundsException: 32 > at com.arjuna.ats.jta.xa.XATxConverter.getSubordinateNodeName(XATxConverter.java:204) > at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca.SubordinateAtomicAction.<init>(SubordinateAtomicAction.java:115) > at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca.TransactionImple.<init>(TransactionImple.java:57) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple.addImportedTransaction(TransactionImporterImple.java:281) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple.importRemoteTransaction(TransactionImporterImple.java:105) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.importTransaction(XATerminatorImple.java:599) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$XAImporterImpl.findOrImportTransaction(JBossLocalTransactionProvider.java:585) > ... 11 more > {noformat} > It appears that there is no protection against an XID of inadequate length in XATxConverter#setSubordinateNodeName. > At present the protocol is attempting to import an XID which contains only the gtid from the master node (based on what I discussed with [~tomjenkinson] some time ago at a previous meeting). This can be changed if it is wrong, but either way this method should fail with a friendlier exception if the XID is not valid for some reason. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2830) Consider possible compensations framework architecture improvements

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2830?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2830: ----------------------------------- Assignee: (was: Tom Jenkinson) > Consider possible compensations framework architecture improvements > ------------------------------------------------------------------- > > Key: JBTM-2830 > URL: https://issues.jboss.org/browse/JBTM-2830 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations > Reporter: Gytis Trikleris > > I've created a document with a list of possible compensations framework improvements. I'm attaching a link to the google doc for you to review and schedule work once appropriate. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2850) Call xa_end on duplicate XAResource as per JTA 1.2 specification

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2850?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2850: ------------------------------------- JTA spec issue is here: https://github.com/javaee/jta-spec/issues/3 > Call xa_end on duplicate XAResource as per JTA 1.2 specification > ---------------------------------------------------------------- > > Key: JBTM-2850 > URL: https://issues.jboss.org/browse/JBTM-2850 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.5.5.Final > > > JTA 1.2 changed requirement: > "A transaction manager is, however, required to implicitly ensure the association of any associated XAResource is ended, via the appropriate XAResource.end call, immediately prior to completion;" > The change is that it no longer is confined to any associated ** resource **, but now specifies any associated ** XAResource ** > What is happening at the moment for two difference instance of an XAR but where isSameRM is true: > Resource1 start TMNOFLAGS > DuplicateResource1 start TMJOIN > Resource2 start TMNOFLAGS > Resource1 end TMSUCCESS > Resource1 prepare > Resource2 end TMSUCCESS > Resource2 prepare > Resource1 commit > Resource2 commit > Post https://java.net/jira/browse/JTA_SPEC-3 this should be: > Resource1 start TMNOFLAGS > DuplicateResource1 start TMJOIN > Resource2 start TMNOFLAGS > Resource1 end TMSUCCESS > DuplicateResource1 end TMSUCCESS > Resource1 prepare > Resource2 end TMSUCCESS > Resource2 prepare > Resource1 commit > Resource2 commit -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2870) Provide way of getting suppressed exceptions out of SubordinateTransaction

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2870?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2870: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1435549|https://bugzilla.redhat.com/show_bug.cgi?id=1435549] from VERIFIED to CLOSED > Provide way of getting suppressed exceptions out of SubordinateTransaction > -------------------------------------------------------------------------- > > Key: JBTM-2870 > URL: https://issues.jboss.org/browse/JBTM-2870 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 4.17.38, 5.5.5.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 4.17.40, 5.2.23.Final, 5.5.7.Final, 5.6.0.Final > > > We need to provide way how to pass suppressed exceptions of of the `SubordinateTransaction` to the caller. > This request came from customer case and https://bugzilla.redhat.com/show_bug.cgi?id=1435549 as we need to provide exceptions thrown from transaction resource. > The interface is used for controlling propagated transaction from one server to another in EAP/WFLY. > Callers are is ejb3 subsystem in EAP 6.4/7.0 and WFTC in EAP 7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 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 reopened JBTM-2905: --------------------------------- > 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.6.2.Final > > > 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, 5 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: -------------------------------- Issue Type: Enhancement (was: Bug) > 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: Enhancement > Components: Tooling > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.6.2.Final > > > 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, 5 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 2017