April 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-711) Make 'ant clean' clean up all artifacts

by Mark Little (JIRA)

Make 'ant clean' clean up all artifacts --------------------------------------- Key: JBTM-711 URL: https://jira.jboss.org/jira/browse/JBTM-711 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Mark Little Assignee: Jonathan Halliday Fix For: 4.11.0 Currently a lot of extraneous artifacts remain. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-733) streamline debug level logging

by Jonathan Halliday (JIRA)

streamline debug level logging ------------------------------ Key: JBTM-733 URL: https://jira.jboss.org/jira/browse/JBTM-733 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common, Configuration Affects Versions: 4.10.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 The debug level logging in JBossTS is unnecessarily complex. DebugLevel values other than 0xffffffff ('ON') and 0x00000000 ('OFF'), FacilityCode and VisibilityLevel filters are largely unused. In practice the use case for debug level logging is for customers to pass trace information back to support. In such cases we inevitably want everything and will filter it later with grep according to the case at hand. The additional verbosity that DebugLevel, FacilityCode and VisibilityLevel add to the codebase is unwarranted. These classes should be nuked. Removing this added complexity will also help make the transition to the new common JBoss logging system (TAG-3) easier. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-724) ensure consistent recovery module passes

by Jonathan Halliday (JIRA)

ensure consistent recovery module passes ---------------------------------------- Key: JBTM-724 URL: https://jira.jboss.org/jira/browse/JBTM-724 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.10.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 PeriodicRecovery should ensure that the same set of modules is used for the first and second pass, as some implementations will not work if only one or the other pass is run. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-723) modularize XARecoveryModule rollback handling

by Jonathan Halliday (JIRA)

modularize XARecoveryModule rollback handling --------------------------------------------- Key: JBTM-723 URL: https://jira.jboss.org/jira/browse/JBTM-723 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.10.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 The XARecoveryModule scans resource managers for in-doubt xids and then determines if they should be rolled back or not. The rules used to determine this are hardcoded and take account only of xids known to JTA top level transactions. More sophisticated, configurable handling is needed for correct functioning of e.g. JTS and JCA inflowed tx. Introduce a pluggable system for determining if in-doubt xids should be rolled back. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-722) TransactionSynchronizationRegistryImple test coverage

by Mark Little (JIRA)

TransactionSynchronizationRegistryImple test coverage ----------------------------------------------------- Key: JBTM-722 URL: https://jira.jboss.org/jira/browse/JBTM-722 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Mark Little Assignee: Jonathan Halliday Fix For: 4.11.0 We need some :-) -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-714) remove orb portability Configuration.java

by Jonathan Halliday (JIRA)

remove orb portability Configuration.java ----------------------------------------- Key: JBTM-714 URL: https://jira.jboss.org/jira/browse/JBTM-714 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 Configuration.java is a relic of the pre-beanification era. Remove it. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-720) Improve MBean test coverage

by Mark Little (JIRA)

Improve MBean test coverage --------------------------- Key: JBTM-720 URL: https://jira.jboss.org/jira/browse/JBTM-720 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing, Transaction Core Reporter: Mark Little Assignee: Jonathan Halliday 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

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-721) Add emma support to jdbc module

by Mark Little (JIRA)

Add emma support to jdbc module ------------------------------- Key: JBTM-721 URL: https://jira.jboss.org/jira/browse/JBTM-721 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Mark Little Assignee: Jonathan Halliday 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

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-635) tackle host and process id lock contention

by Jonathan Halliday (JIRA)

tackle host and process id lock contention ------------------------------------------ Key: JBTM-635 URL: https://jira.jboss.org/jira/browse/JBTM-635 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 The Utility methods for getting host inet addr and process id are heavily used (by Uid creation) and need to be as fast as possible. Revisit caching and synchronization to streamline these. -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-632) tackle ActionManager lock contention

by Jonathan Halliday (JIRA)

tackle ActionManager lock contention ------------------------------------ Key: JBTM-632 URL: https://jira.jboss.org/jira/browse/JBTM-632 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 ActionManager uses a Hashtable for _allActions. Under high load this is becomes a bottleneck. Move to ConcurrentHashMap. -- 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

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2010