July 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-750) replace CLF with jboss-logging

by Jonathan Halliday (JIRA)

replace CLF with jboss-logging ------------------------------ Key: JBTM-750 URL: https://jira.jboss.org/browse/JBTM-750 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common Affects Versions: 4.11.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.12.0 jboss-logging provides an abstraction over 3rd party logging frameworks and i18n, which is pretty much what CLF does. No point in maintaining both and jboss-logging fits the TAG-2 and TAG-3 requirements better. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-728) Add remote tests to emma coverage

by Mark Little (JIRA)

Add remote tests to emma coverage --------------------------------- Key: JBTM-728 URL: https://jira.jboss.org/jira/browse/JBTM-728 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS, Testing Reporter: Mark Little Assignee: Jonathan Halliday Fix For: 4.11.0 The remote tests in JTS were developed to be run manually with specific interceptor options mentioned on the command line. Although they are now junit tests it doesn't seem that all of the options are being used, or perhaps the server side component isn't being covered by emma, because interceptor classes that should be called aren't mentioned in the report. -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-712) Improve test coverage for jta

by Mark Little (JIRA)

Improve test coverage for jta ----------------------------- Key: JBTM-712 URL: https://jira.jboss.org/jira/browse/JBTM-712 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA, Testing Reporter: Mark Little Assignee: Mark Little Fix For: 4.11.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, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-699) Command line interface to modifying transaction log during recovery

by Mark Little (JIRA)

Command line interface to modifying transaction log during recovery ------------------------------------------------------------------- Key: JBTM-699 URL: https://jira.jboss.org/jira/browse/JBTM-699 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery, Tooling, Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.10.0 Similar to the OS browser. -- 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, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBTM-700) Look at restructuring docs

by Mark Little (JIRA)

Look at restructuring docs -------------------------- Key: JBTM-700 URL: https://jira.jboss.org/jira/browse/JBTM-700 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assignee: Mark Little Fix For: 4.11.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, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-678) Enable configuration of XTS using injection of properties into service bean

by Andrew Dinn (JIRA)

Enable configuration of XTS using injection of properties into service bean --------------------------------------------------------------------------- Key: JBTM-678 URL: https://jira.jboss.org/jira/browse/JBTM-678 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.9.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.10.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, 4 months

2
7
0 / 0

[JBoss JIRA] Closed: (JBTM-108) Make number of transactions rolled back per reaper sweep configurable

by Andrew Dinn (JIRA)

[ https://jira.jboss.org/browse/JBTM-108?page=com.atlassian.jira.plugin.sys... ] Andrew Dinn closed JBTM-108. ---------------------------- Resolution: Rejected This doesn't really make sense given the current reaper design which uses the old DYNAMIC mode to decide when to wake up. It only made sense when the wake-up mode was FIXED allowing a lot of cancelled transactions to build up and hten ladnign the reaper with a large burst of work to perform. This situation should not arise often with the latest design (it does not appear to) and even if it does it indicates an app problem -- lots of timed out TXs means the app's TX timeout is misconfigured or the app is overloaded. So, I'm rejecting this because I don't see it as being particularly helpful now and I don't see the point of complicating the behaviour of the reaper merely to help out misconfigured apps. > Make number of transactions rolled back per reaper sweep configurable > --------------------------------------------------------------------- > > Key: JBTM-108 > URL: https://jira.jboss.org/browse/JBTM-108 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Andrew Dinn > Priority: Minor > Fix For: future > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-683) Rework ObjectStore implementations around new interfaces

by Mark Little (JIRA)

Rework ObjectStore implementations around new interfaces -------------------------------------------------------- Key: JBTM-683 URL: https://jira.jboss.org/jira/browse/JBTM-683 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.10.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, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBTM-746) remove config MBean setters

by Jonathan Halliday (JIRA)

remove config MBean setters --------------------------- Key: JBTM-746 URL: https://jira.jboss.org/browse/JBTM-746 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.11.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.12.0 The EnvironmentBeanMBean interfaces have both getters and setters. However, most config variables are read at startup and subsequent modifications don't have an effect on the running system. This is confusing for users, who wonder why changes via the MBean don't seem to work. Remove the setters for now, add then back individually as/when we move to supporting dynamic property updates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-735) provide bean based configuration, part 3

by Jonathan Halliday (JIRA)

provide bean based configuration, part 3 ---------------------------------------- Key: JBTM-735 URL: https://jira.jboss.org/jira/browse/JBTM-735 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.9.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.12.0 Many points in our code read a String property and treat it as a class name to load. Move this functionality to the EnvironmentBeans, so the instantiated class can be retrieved directly. This will reduce classloading duplication and also help with integration to DI frameworks that wish to pass in a pre-instantiated instance of some class. -- 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, 5 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2010