jbossts-issues July 2015

jbossts-issues@lists.jboss.org

1 participants
334 discussions

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-2449: ------------------------------------ Reopening since it is not a duplicate of JBTM 77 > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-2449. ---------------------------------- Resolution: Duplicate Issue Duplicate of JBTM-77 > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2449: -------------------------------------- Summary: SPI class ServerVMClientUserTransaction should be Serializable and Referenceable Key: JBTM-2449 URL: https://issues.jboss.org/browse/JBTM-2449 Project: JBoss Transaction Manager Issue Type: Bug Components: SPI Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

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

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2443?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2443: ---------------------------------------- Adding link since the change is partially undoing a prior fix > 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.next > > > 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, 5 months

1
0
0 / 0

← Newer
1
...
31
32
33
34
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2015