March 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2864) Add more tests for the JTS implementation of ExtendedJBossXATerminator

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2864?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2864: ----------------------------------- Description: ExtendedJBossXATerminator is our (extended) SPI interface for importing transactions and it has both JTA and JTS implementations. It is used by EJB in JTA mode which will be fully exercising the interface in JTA mode. However, we only test a subset of the interface in JTS mode (see com.arjuna.ats.jta.distributed.SimpleIsolatedServers) and these need extending to cover all of the methods. Note that at least one of the methods is known not to produce the correct result, namely {quote} public Transaction getTransaction(Xid xid) throws XAException {quote} because the implementation uses XATxConverter to lookup the transaction but XATxConverter uses a different Xid format id from the one used by JTS so it will return null (instead of the transaction corresponding to the input xid). was:ExtendedJBossXATerminator is our (extended) SPI interface for importing transactions and it has both JTA and JTS implementations. It is used by EJB in JTA mode which will be fully exercising the interface in JTA mode. However, we only test a subset of the interface in JTS mode (see com.arjuna.ats.jta.distributed.SimpleIsolatedServers) and these need extending to cover all of the methods. > Add more tests for the JTS implementation of ExtendedJBossXATerminator > ---------------------------------------------------------------------- > > Key: JBTM-2864 > URL: https://issues.jboss.org/browse/JBTM-2864 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > ExtendedJBossXATerminator is our (extended) SPI interface for importing transactions and it has both JTA and JTS implementations. It is used by EJB in JTA mode which will be fully exercising the interface in JTA mode. However, we only test a subset of the interface in JTS mode (see com.arjuna.ats.jta.distributed.SimpleIsolatedServers) and these need extending to cover all of the methods. > Note that at least one of the methods is known not to produce the correct result, namely > {quote} > public Transaction getTransaction(Xid xid) throws XAException > {quote} > because the implementation uses XATxConverter to lookup the transaction but XATxConverter uses a different Xid format id from the one used by JTS so it will return null (instead of the transaction corresponding to the input xid). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2864) Add more tests for the JTS implementation of ExtendedJBossXATerminator

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2864?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2864: ----------------------------------- Priority: Major (was: Minor) > Add more tests for the JTS implementation of ExtendedJBossXATerminator > ---------------------------------------------------------------------- > > Key: JBTM-2864 > URL: https://issues.jboss.org/browse/JBTM-2864 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > ExtendedJBossXATerminator is our (extended) SPI interface for importing transactions and it has both JTA and JTS implementations. It is used by EJB in JTA mode which will be fully exercising the interface in JTA mode. However, we only test a subset of the interface in JTS mode (see com.arjuna.ats.jta.distributed.SimpleIsolatedServers) and these need extending to cover all of the methods. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2864) Add more tests for the JTS implementation of ExtendedJBossXATerminator

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2864?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2864: ------------------------------------- In particular we should check the use of XidImple(xid).getTransactionUID which I think would only work for JTA (not JTS) > Add more tests for the JTS implementation of ExtendedJBossXATerminator > ---------------------------------------------------------------------- > > Key: JBTM-2864 > URL: https://issues.jboss.org/browse/JBTM-2864 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > ExtendedJBossXATerminator is our (extended) SPI interface for importing transactions and it has both JTA and JTS implementations. It is used by EJB in JTA mode which will be fully exercising the interface in JTA mode. However, we only test a subset of the interface in JTS mode (see com.arjuna.ats.jta.distributed.SimpleIsolatedServers) and these need extending to cover all of the methods. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2864) Add more tests for the JTS implementation of ExtendedJBossXATerminator

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2864: -------------------------------------- Summary: Add more tests for the JTS implementation of ExtendedJBossXATerminator Key: JBTM-2864 URL: https://issues.jboss.org/browse/JBTM-2864 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Affects Versions: 5.5.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.later ExtendedJBossXATerminator is our (extended) SPI interface for importing transactions and it has both JTA and JTS implementations. It is used by EJB in JTA mode which will be fully exercising the interface in JTA mode. However, we only test a subset of the interface in JTS mode (see com.arjuna.ats.jta.distributed.SimpleIsolatedServers) and these need extending to cover all of the methods. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2858) Transaction bridging for REST-AT not working because of switch to new wfly transaction client

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2858?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2858: ------------------------------------- Needs revert of https://github.com/jbosstm/narayana/pull/1142 > Transaction bridging for REST-AT not working because of switch to new wfly transaction client > --------------------------------------------------------------------------------------------- > > Key: JBTM-2858 > URL: https://issues.jboss.org/browse/JBTM-2858 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.5.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > Fix For: 5.next > > > Transaction bridging (RTS <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client). > The cause code change could be checked here > https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b... > Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2853) Transaction bridging for WS not working because of switch to new wfly transaction client

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2853?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2853: ------------------------------------- Needs revert of https://github.com/jbosstm/narayana/pull/1142 > Transaction bridging for WS not working because of switch to new wfly transaction client > ---------------------------------------------------------------------------------------- > > Key: JBTM-2853 > URL: https://issues.jboss.org/browse/JBTM-2853 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > Fix For: 5.next > > > Transaction bridging (WS transaction <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client). > The cause code change could be checked here > https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b... > Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. The similar thing will probably need to be done for opposite side. > Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2863) Bug in SPI for tracking transaction state association changes

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2863?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #22 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Bug in SPI for tracking transaction state association changes > ------------------------------------------------------------- > > Key: JBTM-2863 > URL: https://issues.jboss.org/browse/JBTM-2863 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.5.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > JBTM-2343 introduced a feature for observing transaction state changes (requested by JPA). Listeners register interest in particular events (ASSOCIATED and DISASSOCIATING). However, BaseTransactionManagerDelegate will notify listeners for either event even if they only subscribed for one of them. For example if a listener subscribes for thread to transaction associations only it will also receive disassociation notifications. > In addition, the current event types are restricted to a single java enum (org.jboss.tm.listener.EventType). Since java enums are not extensible the solution needs to be tweaked so that we can easily add new event types. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2863) Bug in SPI for tracking transaction state association changes

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2863: -------------------------------------- Summary: Bug in SPI for tracking transaction state association changes Key: JBTM-2863 URL: https://issues.jboss.org/browse/JBTM-2863 Project: JBoss Transaction Manager Issue Type: Bug Components: SPI Affects Versions: 5.5.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later JBTM-2343 introduced a feature for observing transaction state changes (requested by JPA). Listeners register interest in particular events (ASSOCIATED and DISASSOCIATING). However, BaseTransactionManagerDelegate will notify listeners for either event even if they only subscribed for one of them. For example if a listener subscribes for thread to transaction associations only it will also receive disassociation notifications. In addition, the current event types are restricted to a single java enum (org.jboss.tm.listener.EventType). Since java enums are not extensible the solution needs to be tweaked so that we can easily add new event types. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 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 March 2017