January 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1719) Improve test coverage for REST-AT multiplexor.

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-1719?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-1719: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Improve test coverage for REST-AT multiplexor. > ---------------------------------------------- > > Key: JBTM-1719 > URL: https://issues.redhat.com/browse/JBTM-1719 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Implement more unit and integration tests to cover more aspects of multiplexor functionality (https://github.com/jbosstm/narayana/tree/master/rts/at/integration). Especially recovery. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1801) Move all test properties into root pom.xml

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-1801?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-1801: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Move all test properties into root pom.xml > ------------------------------------------ > > Key: JBTM-1801 > URL: https://issues.redhat.com/browse/JBTM-1801 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Paul Robinson > Priority: Trivial > Fix For: 5.next > > > We have these test properties duplicated in many places: > https://github.com/jbosstm/narayana/blob/master/XTS/localjunit/pom.xml#L22 > We should move them up to the root pom.xml to simplify maintenance. As part of this task you need to hunt out all these usages and similar. Then come up with a common set of properties that works in all cases and move to the root pom.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1853) RESTAT does not expose recovery URIs after a crash

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-1853?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-1853: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > RESTAT does not expose recovery URIs after a crash > -------------------------------------------------- > > Key: JBTM-1853 > URL: https://issues.redhat.com/browse/JBTM-1853 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > The RESTAT coordinator creates a participant-recovery URI during participant enlistment. This URI should exist for as long as the participant participates in the transaction including during recovery time. After a coordinator crash GET requests return 404 instead of returning the participant resource URI -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1922) RTS error and warning messages do have unique codes for identification purposes

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-1922?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-1922: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > RTS error and warning messages do have unique codes for identification purposes > ------------------------------------------------------------------------------- > > Key: JBTM-1922 > URL: https://issues.redhat.com/browse/JBTM-1922 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.0.0.M4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > > ANDIAMO-7 says that all error and warning messages should have a unique code that can be used to identify them. RTS does not conform with this requirement. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-2110?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-2110: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.redhat.com/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2137) Failed CI job because JDBCStore recovery was stalled

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-2137?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-2137: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Failed CI job because JDBCStore recovery was stalled > ---------------------------------------------------- > > Key: JBTM-2137 > URL: https://issues.redhat.com/browse/JBTM-2137 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Recovery > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The linked CI job failed because the STATESTOREJBOSSTSTXTABLE had too many entries (>600) and this caused the recovery pass to take about 15 minutes which in turn causes subsequent tests to time out. The reason for so many entries is covered by JBTM-2133 but this JIRA is for the poor performance when there are so many entries. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-2124?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-2124: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.redhat.com/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > Attachments: jonathan-picturing-trouble-of-subordinate-txn-for-jts-orphan-detection.jpg > > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2183) Need finer grained control over which XAResource is used for recovery

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-2183?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-2183: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Need finer grained control over which XAResource is used for recovery > --------------------------------------------------------------------- > > Key: JBTM-2183 > URL: https://issues.redhat.com/browse/JBTM-2183 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Recovery > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > During recovery when we recreate an XAResource we need one which knows about the xid that is being recovered. We implement this in the XARecoveryModule which calls recover() on each resource returned by registered XA recovery helpers. If the xid returned from recover matches against the one we are recovering we use that XAResource to drive recovery. > However, some RMs will return all prepared transaction branches and not just the ones specific to the particular resource we made the recover call on. The scenario that led to the issue was configuring 2 datasources against the same database but with different credentials. If we replay the commit on the "wrong" one we get ORA-24774: "The transaction specified in the call refers to a transaction created by a different user". > The fix is to return an XA resource that matches the JNDI name we logged in the recovery record and if the JNDI name is not available we drop back to using the current solution (note that the name is available when running in wildfly/EAP) . > And finally, I I wonder if we want to make this new behaviour optional? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2116) SPI: Unique identifier for a transaction

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-2116?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-2116: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > SPI: Unique identifier for a transaction > ---------------------------------------- > > Key: JBTM-2116 > URL: https://issues.redhat.com/browse/JBTM-2116 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The Narayana SPI should provide a method that returns a unique identifier for a transaction that is stable for its entire lifecycle. > {noformat} > public Object getIdentifier(Transaction tx) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1715) NPE when using CompensationManager within an in-flowed WS-BA transaction

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-1715?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-1715: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > NPE when using CompensationManager within an in-flowed WS-BA transaction > ------------------------------------------------------------------------ > > Key: JBTM-1715 > URL: https://issues.redhat.com/browse/JBTM-1715 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Paul Robinson > Priority: Minor > Fix For: 5.next > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The following error occurs if an injected CompensationManager is invoked within the scope of a compensation-based transaction that was in-flowed via a WS-BA transaction. > {quote} > 16:17:09,879 ERROR [org.jboss.as.ejb3.invocation] (default task-18) JBAS014134: EJB Invocation failed on component TestServiceService for method public void org.jboss.narayana.compensations.functiona[617/9100] > ted.TestServiceService.saveDataCancelOnFailure(java.lang.Boolean): javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:251) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:215) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPS > HOT] > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 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 January 2020