July 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2461) Allow multiple configurations of Narayana to execute in the same JVM

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2461: ----------------------------------- Summary: Allow multiple configurations of Narayana to execute in the same JVM Key: JBTM-2461 URL: https://issues.jboss.org/browse/JBTM-2461 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Tom Jenkinson Assignee: Tom Jenkinson A long running feature request that I can't locate in Jira so recording here. Future revisions of the application container WildFly would find it beneficial to run multiple instances of the transaction manager in different configurations (one-per app) and allow the service to be started/stopped/executed in isolation. One of the barriers is that the factory method returns a singleton. The second is that there is static state in classes and so different configs are not viable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2459: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2459: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2443) Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2443?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2443: ------------------------------------- Previously if RMFAIL was returned out of XAResource.commit(true, xid1) we did not return an exception and left it to the database to resolve the issue and potentially leave it to return the Xid during recovery using some assistance from its client side driver for example. The new behaviour would allow the database to do that the same as it does today but an exception would also be thrown to the client to say that there is a HeuristicMixed to be aware the result of the commit may not be reliable. > Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL > ------------------------------------------------------------------------- > > Key: JBTM-2443 > URL: https://issues.jboss.org/browse/JBTM-2443 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.0 > > > If a one phase commit is performed on an XAResource and it raises RMFAIL we have no way to know whether the resource committed or rolled back. We currently do not raise an exception in this scenario as an interpretation of the XA spec allows us to. > We have had community feedback that this has an issue for user applications and having consulted with the rest of our community and no negative comments received we will modify the behavior so that this scenario results in the closest exception that JTA allows HeuristicMixed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2460: ------------------------------------- Bind in JNDI? > Expose TransactionListenerRegistry via the SPI > ---------------------------------------------- > > Key: JBTM-2460 > URL: https://issues.jboss.org/browse/JBTM-2460 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: > {code} > (TransactionListenerRegistry) getTransactionManager(); > {code} > So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2460: ----------------------------------- Fix Version/s: 5.next > Expose TransactionListenerRegistry via the SPI > ---------------------------------------------- > > Key: JBTM-2460 > URL: https://issues.jboss.org/browse/JBTM-2460 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: > {code} > (TransactionListenerRegistry) getTransactionManager(); > {code} > So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2460: -------------------------------------- Summary: Expose TransactionListenerRegistry via the SPI Key: JBTM-2460 URL: https://issues.jboss.org/browse/JBTM-2460 Project: JBoss Transaction Manager Issue Type: Bug Components: SPI Reporter: Michael Musgrove Assignee: Michael Musgrove TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: {code} (TransactionListenerRegistry) getTransactionManager(); {code} So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 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: -------------------------------- Issue Type: Feature Request (was: Task) > Add support for XADisk > ---------------------- > > Key: JBTM-1965 > URL: https://issues.jboss.org/browse/JBTM-1965 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Student project > Affects Versions: 5.0.0.M5 > Reporter: Mark Little > Fix For: 6.later > > > We're unlikely to maintain fileio but there may be a need for supporting some transactional file interactions. XADisk (https://xadisk.java.net/) seems to have a vibrant user community, so we should take a look at this. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.... ] Work on JBTM-2245 started by Michael Musgrove. ---------------------------------------------- > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2459) Add an option to allow JBTM-2443 to be enabled in 4.17

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2459?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2459: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/887 > Add an option to allow JBTM-2443 to be enabled in 4.17 > ------------------------------------------------------ > > Key: JBTM-2459 > URL: https://issues.jboss.org/browse/JBTM-2459 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Configuration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.30 > > > JBTM-2443 should not be the default behavior in 4.x series but would be useful to allow it to be enabled to assist with migration to 5.x where it is the default and only option. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 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 July 2015