July 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2680) Document compensations API

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2680?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2680: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.6.4.Final Resolution: Done > Document compensations API > -------------------------- > > Key: JBTM-2680 > URL: https://issues.jboss.org/browse/JBTM-2680 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations, Documentation > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > Fix For: 5.6.4.Final > > > There is no documentation for compensations API in our docs. Most of the things are covered in the quickstarts and blog, but adding something to the docs would be good too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1965) Add support for XADisk

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1965?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1965: -------------------------------- Labels: (was: available student) > Add support for XADisk > ---------------------- > > Key: JBTM-1965 > URL: https://issues.jboss.org/browse/JBTM-1965 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Affects Versions: 5.0.0.M5 > Reporter: Mark Little > > Transactions are often used to structure activities within reliable software applications. In Java EE, business logic typically involves accessing transactional resource managers (databases, message queues) within boundaries denoted by calls to the JTA (begin/commit/rollback). The resource managers work with the transaction manager to perform e.g. locking, logging and recovery transparently to the application programmer. However, this separation of concerns is broken with regard to one important resource: the file system. Java's file I/O library does not support transactions, a situation which requires application programmers to implement such support manually in their programs. In this project you will develop a transaction aware resource manager for file I/O in Java. This library will provide application programmers with access to a filesystem that offers ACID semantics. > We already have a transactional file I/O implementation but there are now alternatives available. XADisk (https://xadisk.java.net/) seems to have a vibrant user community, so we should take a look at this. Part of the work will be to compare and contrast the options available. > To undertake this project you should have a good understanding of Java file I/O and some knowledge of transactions (ACID semantics and the JTA). The work will be open source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1488) Implement the REST-JDI specification

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1488?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1488: ----------------------------------- Labels: (was: student) > Implement the REST-JDI specification > ------------------------------------ > > Key: JBTM-1488 > URL: https://issues.jboss.org/browse/JBTM-1488 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 6.later > > > https://community.jboss.org/wiki/CompensatingRESTfulTransactions/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2919) Add a default jbossts-properties.xml into the Tomcat uber jar

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2919: ----------------------------------- Summary: Add a default jbossts-properties.xml into the Tomcat uber jar Key: JBTM-2919 URL: https://issues.jboss.org/browse/JBTM-2919 Project: JBoss Transaction Manager Issue Type: Bug Components: Application Server Integration Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next There is no jbossts-properties.xml in tomcat-jta Uber jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2918) Allow setting IsSameRMOverride as default

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2918: ----------------------------------- Summary: Allow setting IsSameRMOverride as default Key: JBTM-2918 URL: https://issues.jboss.org/browse/JBTM-2918 Project: JBoss Transaction Manager Issue Type: Component Upgrade Components: Transactional Driver Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next When transactional driver was first written the IsSameRMOverride was not required as the default but with current databases it makes a sensible default. Provide a config option to easily set this as the default. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2918) Allow setting IsSameRMOverride as default

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2918?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2918: -------------------------------- Issue Type: Enhancement (was: Component Upgrade) > Allow setting IsSameRMOverride as default > ----------------------------------------- > > Key: JBTM-2918 > URL: https://issues.jboss.org/browse/JBTM-2918 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transactional Driver > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > When transactional driver was first written the IsSameRMOverride was not required as the default but with current databases it makes a sensible default. Provide a config option to easily set this as the default. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2680) Document compensations API

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2680?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when chalda created pull request #45 in GitHub ----------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Document compensations API > -------------------------- > > Key: JBTM-2680 > URL: https://issues.jboss.org/browse/JBTM-2680 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Compensations, Documentation > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > > There is no documentation for compensations API in our docs. Most of the things are covered in the quickstarts and blog, but adding something to the docs would be good too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2916) Disable dynamic1PC for subordinate transactions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2916?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2916. --------------------------------- Resolution: Done > Disable dynamic1PC for subordinate transactions > ----------------------------------------------- > > Key: JBTM-2916 > URL: https://issues.jboss.org/browse/JBTM-2916 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.2.25.Final, 5.next, 5.5.28.Final > > > If there are two resources in a BasicAction there is an optimization that will cause the second resource to commit during prepare if the first resource returns XARD_ONLY. > This can cause data inconsistency in a transaction comprising of subordinates where the phase 2 decision is rollback. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 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 closed JBTM-2908. ------------------------------- Resolution: Done > 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.2.24.Final, 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.5.25.Final, 5.6.2.Final > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2907) Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2907?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2907: -------------------------------- Fix Version/s: 5.5.25.Final (was: 5.2.25.Final) > Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2907 > URL: https://issues.jboss.org/browse/JBTM-2907 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.24.Final, 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > Fix For: 5.6.2.Final, 5.5.25.Final > > > When RAR calls {{XATerminator.recover(int)}} the call chain is not directed to Narayana implementation of XATerminator but it's passed to WFTC where {{ExtendedJBossXATerminator}} method {{doRecover}} is called. But the {{doRecover}} does not provide the expected recovery call - e.g. it does not accept flags ({{XAResource.TMSTARTRSCAN}}, {{XAResource.TMENDRSCAN}}) to drive the whole recovery process in case. > The biggest functionality trouble is for JTS where {{XATerminatorImple}} does not implement intentionally the {{doRecover}} function (https://github.com/jbosstm/narayana/blob/5.5.24.Final/ArjunaJTS/jtax/clas...). Thus RAR using call {{XATerminator.recover}} when JTS is under use does nothing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 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 July 2017