July 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1336) DUPID detection for mysql in JTS mode does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1336?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1336: -------------------------------- Fix Version/s: (was: 5.0.0.M4) > DUPID detection for mysql in JTS mode does not work > --------------------------------------------------- > > Key: JBTM-1336 > URL: https://issues.jboss.org/browse/JBTM-1336 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Attachments: JBTM-1336.patch > > Original Estimate: 3 days > Time Spent: 1 day > Remaining Estimate: 2 days > > Mysql does not send errorcode of XAException.XAER_DUPID, it sends 0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1336) DUPID detection for mysql in JTS mode does not work

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1336?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1336: -------------------------------- Assignee: (was: Tom Jenkinson) > DUPID detection for mysql in JTS mode does not work > --------------------------------------------------- > > Key: JBTM-1336 > URL: https://issues.jboss.org/browse/JBTM-1336 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Tom Jenkinson > Priority: Minor > Attachments: JBTM-1336.patch > > Original Estimate: 3 days > Time Spent: 1 day > Remaining Estimate: 2 days > > Mysql does not send errorcode of XAException.XAER_DUPID, it sends 0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1042) GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1042?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1042: -------------------------------- Assignee: Paul Robinson > GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES) > -------------------------------------------------------------------------------------- > > Key: JBTM-1042 > URL: https://issues.jboss.org/browse/JBTM-1042 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M4 > > > 1.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple Line 132 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.isParticipantPresent(Uid) > 2.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple Line 128 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple.isParticipantPresent(Uid) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1042) GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1042?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1042: -------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.Final) > GC: No relationship between generic parameter and method argument (GC_UNRELATED_TYPES) > -------------------------------------------------------------------------------------- > > Key: JBTM-1042 > URL: https://issues.jboss.org/browse/JBTM-1042 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Priority: Minor > Fix For: 5.0.0.M4 > > > 1.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple Line 132 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.isParticipantPresent(Uid) > 2.XTS/recovery > org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple Line 128 > com.arjuna.ats.arjuna.common.Uid is incompatible with expected argument type String in org.jboss.jbossts.xts.recovery.participant.ba.XTSBARecoveryManagerImple.isParticipantPresent(Uid) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-846) Allow multiple transaction managers with different configurations to operate in a single JVM

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-846: ------------------------------- Assignee: Paul Robinson (was: Gytis Trikleris) > Allow multiple transaction managers with different configurations to operate in a single JVM > -------------------------------------------------------------------------------------------- > > Key: JBTM-846 > URL: https://issues.jboss.org/browse/JBTM-846 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This will require removal of much of the static configuration state such as StateManager references to ObjectStore -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-846) Allow multiple transaction managers with different configurations to operate in a single JVM

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-846: ------------------------------- Priority: Major (was: Minor) > Allow multiple transaction managers with different configurations to operate in a single JVM > -------------------------------------------------------------------------------------------- > > Key: JBTM-846 > URL: https://issues.jboss.org/browse/JBTM-846 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This will require removal of much of the static configuration state such as StateManager references to ObjectStore -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-846) Allow multiple transaction managers with different configurations to operate in a single JVM

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-846: ------------------------------- Description: This will require removal of much of the static configuration state such as StateManager references to ObjectStore > Allow multiple transaction managers with different configurations to operate in a single JVM > -------------------------------------------------------------------------------------------- > > Key: JBTM-846 > URL: https://issues.jboss.org/browse/JBTM-846 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This will require removal of much of the static configuration state such as StateManager references to ObjectStore -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1802) Consider moving Arquillian profiles to root pom.xml

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1802?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1802: -------------------------------- Component/s: Testing > Consider moving Arquillian profiles to root pom.xml > --------------------------------------------------- > > Key: JBTM-1802 > URL: https://issues.jboss.org/browse/JBTM-1802 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, Testing > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M4 > > > We have three Arquillian profiles (for managed, remote and ipv6-managed) present in the pom of nearly every test that uses Arquillian. I suspect they can all be identical and thus placed int he root pom.xml. This should simplify maintenance and will ensure any fixes to this config are made throughout. > The problem is that we may have legitimate reasons for this config to differ for some tests. Maybe we could use overrides in these cases. > Assigning to Tom for his input. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-846) Allow multiple transaction managers with different configurations to operate in a single JVM

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-846?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-846: ------------------------------- Summary: Allow multiple transaction managers with different configurations to operate in a single JVM (was: Remove static initializers) > Allow multiple transaction managers with different configurations to operate in a single JVM > -------------------------------------------------------------------------------------------- > > Key: JBTM-846 > URL: https://issues.jboss.org/browse/JBTM-846 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA, JTS, Recovery, Transaction Core, XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1575) Test support for Informix

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1575?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1575: -------------------------------- Component/s: BlackTie > Test support for Informix > ------------------------- > > Key: JBTM-1575 > URL: https://issues.jboss.org/browse/JBTM-1575 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: BlackTie, Testing > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Optional > Fix For: 5.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2013