July 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-230) Put xaRecoveryNode in configuration

by Mark Little (JIRA)

Put xaRecoveryNode in configuration ----------------------------------- Key: JBTM-230 URL: http://jira.jboss.com/jira/browse/JBTM-230 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP4 Reporter: Mark Little Assigned To: Mark Little Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-581) Replacement for XML comments in default recovery properties

by Mark Little (JIRA)

Replacement for XML comments in default recovery properties ----------------------------------------------------------- Key: JBTM-581 URL: https://jira.jboss.org/jira/browse/JBTM-581 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Transaction Core Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Jonathan Halliday Fix For: 4.8.0 default-RecoveryManager and friends used to exist in etc. They contained comments that described the various properties. These are discussed in the docs, but were useful within a text file as these. Should provide an equivalent now that these files have been deleted. Like it or not, these were part of the public "API" and may be missed by developers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-582) Change node name separator for Xid

by Mark Little (JIRA)

Change node name separator for Xid ---------------------------------- Key: JBTM-582 URL: https://jira.jboss.org/jira/browse/JBTM-582 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little Priority: Minor Fix For: 4.8.0 Currently is '-' which causes problems when - is a valid part of a Uid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-579) DisposeRecord doSave return wrong value

by Mark Little (JIRA)

DisposeRecord doSave return wrong value --------------------------------------- Key: JBTM-579 URL: https://jira.jboss.org/jira/browse/JBTM-579 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little Fix For: 4.8.0 Should return true. That line was commented out and it was returning false. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-577) uidToOtid sets incorrect bqual

by Mark Little (JIRA)

uidToOtid sets incorrect bqual ------------------------------ Key: JBTM-577 URL: https://jira.jboss.org/jira/browse/JBTM-577 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little Fix For: 4.8.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
5
0 / 0

[JBoss JIRA] Updated: (JBTM-112) Add QA tests to check default timeout behaviour

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-112?page=com.atlassian.jira.plugi... ] Mark Little updated JBTM-112: ----------------------------- Fix Version/s: 5.0.0 (was: 4.8.0) > Add QA tests to check default timeout behaviour > ----------------------------------------------- > > Key: JBTM-112 > URL: https://jira.jboss.org/jira/browse/JBTM-112 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-134) Update the property manager xsd

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-134?page=com.atlassian.jira.plugi... ] Mark Little closed JBTM-134. ---------------------------- Resolution: Out of Date With recent changes on flattening the property file structure this becomes OOD. > Update the property manager xsd > ------------------------------- > > Key: JBTM-134 > URL: https://jira.jboss.org/jira/browse/JBTM-134 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Release Process > Reporter: Mark Little > Assignee: Mark Little > Fix For: 4.8.0 > > > The schemas for the property manager are out of date. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBTM-99) Fine grained control over setTransactionTimeout execution

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-99?page=com.atlassian.jira.plugin... ] Mark Little updated JBTM-99: ---------------------------- Fix Version/s: future (was: 4.8.0) > Fine grained control over setTransactionTimeout execution > --------------------------------------------------------- > > Key: JBTM-99 > URL: https://jira.jboss.org/jira/browse/JBTM-99 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS > Affects Versions: 4.2 > Reporter: Kevin Conner > Assignee: Mark Little > Fix For: future > > > We need to add fine grained control to the transaction timeout handling code. > Areas covered by this include > - transaction inflow > - timeout propagation to resources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-438) Consider flattening the property file (again)

by Mark Little (JIRA)

Consider flattening the property file (again) --------------------------------------------- Key: JBTM-438 URL: https://jira.jboss.org/jira/browse/JBTM-438 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little At one time the configuration file was relatively straightforward. Then we added support for nested scopes and dependencies between scopes. This is overkill these days, so we should consider going back to a nice straightforward property file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-535) CLONE -make RecoveryManager restartable

by Mauro Molinari (JIRA)

CLONE -make RecoveryManager restartable --------------------------------------- Key: JBTM-535 URL: https://jira.jboss.org/jira/browse/JBTM-535 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Application Server Integration, Recovery Affects Versions: 4.5.0 Reporter: Mauro Molinari Assignee: Jonathan Halliday Fix For: 4.6.0 Stopping and restarting the transaction manager inside JBossAS causes problems, because the recovery system does not like to be restarted once it is stopped: java.lang.IllegalThreadStateException at java.lang.Thread.start(Thread.java:571) at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.start(RecoveryManagerImple.java:236) at com.arjuna.ats.arjuna.recovery.RecoveryManager.startRecoveryManagerThread(RecoveryManager.java:226) at com.arjuna.ats.jbossatx.jts.TransactionManagerService.start(TransactionManagerService.java:285) Options would seem to be disposing the static singleton _recoveryManager in RecoveryManager and recreating it on the next start, effectively causing a new RecoveryManagerImple to be instantiated, or keep the RecoveryManagerImple instance and rework its impl so that the PeriodicRecovery _periodicRecovery is disposed and recreated on restart. Either one has slightly odd semantics as the PeriodicRecovery is a Thread (which can't be restarted so has to be replaced) and also the object that has the module list and the server socket, so disposal and/or recreation of this state will be needed on restart. Maybe better to rename stop() to dispose() or something similarly final, to indicate the semantics are 'throw this away and start again' rather than giving the impression that stop/start == suspend/resume which is misleading. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2009