October 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-627) refactor AbstractRecord sort order handling

by Jonathan Halliday (JIRA)

refactor AbstractRecord sort order handling ------------------------------------------- Key: JBTM-627 URL: https://jira.jboss.org/jira/browse/JBTM-627 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Transaction Core Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 AbstractRecords can be ordering using one of two different algorithms. The configuration setting is read on each comparison, which is expensive. It should be read at startup and cached. The config should come via the new beans mechanism, not a build time setting. -- 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

[JBoss JIRA] Created: (JBTM-595) Add support for JBoss LogManager backend

by David Lloyd (JIRA)

Add support for JBoss LogManager backend ---------------------------------------- Key: JBTM-595 URL: https://jira.jboss.org/jira/browse/JBTM-595 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Common Reporter: David Lloyd Priority: Minor The new log manager in AS 6.0 supports internationalization and localization natively. Provide an implementation which does not rely on log4j or JCL anymore since those technologies are bug-ridden and obsolete. Patch attached. -- 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

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-555) make memory leak tests more robust

by Jonathan Halliday (JIRA)

make memory leak tests more robust ---------------------------------- Key: JBTM-555 URL: https://jira.jboss.org/jira/browse/JBTM-555 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing, Transaction Core Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: future Some tests in the txcore group attempt to detect memory leaks by setup System.gc() take memory reading doTransactionStuff System.gc() take another memory reading This is unreliable, as System.gc() is only advisory to the runtime. There is no way to FORCE gc from within the jvm. This causes the tests to be somewhat unreliable. Dirty tricks to work around this include running the tests with a small heap (-Xmx5m). With less free space to work with, the gc tries harder. On a default size heap it mostly ignores System.gc(). Unfortunately the test framework does not make it easy to set -Xmx on a per test / test group basis. Similar effect could perhaps be achieved by allocating all except a small portion of the available heap from within the vm using eg. new byte[]. There is also the jvmti ForceGarbageCollection method, but that would require us to have a chunk of C code on each test platform, which is a pain. -- 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

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-637) remove obsolete JDBC code

by Jonathan Halliday (JIRA)

remove obsolete JDBC code ------------------------- Key: JBTM-637 URL: https://jira.jboss.org/jira/browse/JBTM-637 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 The JDBC module contains much deprecated code, mainly plugins to work around issues in 3rd party drivers we no longer test or support anyhow. The more recent versions of the drivers are more spec compliant and no longer force us to jump through so many hoops. Remove the obsolete hoop jumping code. -- 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

[JBoss JIRA] Created: (JBTM-638) clean up CLF

by Jonathan Halliday (JIRA)

clean up CLF ------------ Key: JBTM-638 URL: https://jira.jboss.org/jira/browse/JBTM-638 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 CLF is an unnecessarily complex mess. Throw out the unused bits and rework the factory mechanism to make it more flexible (needed for JBTM-595). Cleaning up the API usage (JBTM-612 and other issue) will probably help too. Ensure no runtime dep on commons logging unless it is selected via config. -- 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

[JBoss JIRA] Created: (JBTM-612) check use of isDebugEnabled/debugAllowed

by Jonathan Halliday (JIRA)

check use of isDebugEnabled/debugAllowed ---------------------------------------- Key: JBTM-612 URL: https://jira.jboss.org/jira/browse/JBTM-612 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9 The CLF exposes an rather complex API, in which isDebugEnabled and debugAllowed have different semantics. As pretty much everything is logged, the cost of these methods, and especially the cost of incorrect usage that leads to creating debug messages that just get throw away, is a non-trivial overhead. Both the implementation of these methods and their usage is suspect and needs a review. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBTM-626) make EnvironmentBean fields volatile

by Jonathan Halliday (JIRA)

make EnvironmentBean fields volatile ------------------------------------ Key: JBTM-626 URL: https://jira.jboss.org/jira/browse/JBTM-626 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 The EnvironmentBeans are accessed from multiple threads, so fields need to be volatile or stale values may be read, which can cause some wonderfully difficult to debug problems. -- 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

[JBoss JIRA] Created: (JBTM-414) atsintegration classes not internationalized

by Mark Little (JIRA)

atsintegration classes not internationalized -------------------------------------------- Key: JBTM-414 URL: https://jira.jboss.org/jira/browse/JBTM-414 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-418) ExpiredEntryScanner does not delete old state after move

by Mark Little (JIRA)

ExpiredEntryScanner does not delete old state after move -------------------------------------------------------- Key: JBTM-418 URL: https://jira.jboss.org/jira/browse/JBTM-418 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: 4.5 -- 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
6
0 / 0

[JBoss JIRA] Created: (JBTM-300) Move stale transaction logs

by Mark Little (JIRA)

Move stale transaction logs --------------------------- Key: JBTM-300 URL: http://jira.jboss.com/jira/browse/JBTM-300 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assigned To: Mark Little Priority: Optional We should generalise the ExpiryScanner implementation of TopLevelTransaction in JTS so that logs that cannot be recovered after a set period of time are moved elsewhere for manual intervention. -- 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, 5 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2009