March 2010 - jbossts-issues - Jboss List Archives

[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, 8 months

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, 8 months

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, 8 months

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, 8 months

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, 8 months

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, 8 months

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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-613) TxControl.getStore should not recreate ObjectStore on each call

by Jonathan Halliday (JIRA)

TxControl.getStore should not recreate ObjectStore on each call --------------------------------------------------------------- Key: JBTM-613 URL: https://jira.jboss.org/jira/browse/JBTM-613 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.8.0 The TxControl.getStore method creates a new ObjectStore instance each time it's called i.e. for every tx. Since creation steps though some complex and highly synchronized inventory/naming code, it's expensive. The store instance should be created once and cached by TxControl. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-734) Backport locking mechanism from JBTM-289

by Justin Bertram (JIRA)

Backport locking mechanism from JBTM-289 ---------------------------------------- Key: JBTM-734 URL: https://jira.jboss.org/jira/browse/JBTM-734 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.2.3.CP09 Reporter: Justin Bertram Assignee: Justin Bertram Fix For: 4.2.3.CP10 The locking strategy from JBTM-289 committed in revision 1495 (http://fisheye.jboss.org/changelog/JBossTS/?cs=14945) needs to be backported for use in EAP 4.x. -- 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-530) Thrown Exceptions often loose the original cause

by Davide Cavestro (JIRA)

Thrown Exceptions often loose the original cause ------------------------------------------------ Key: JBTM-530 URL: https://jira.jboss.org/jira/browse/JBTM-530 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5.0 Reporter: Davide Cavestro In JBossTM exceptions are often catched and left behind in favor of a new dedicated Exception (or Error) contextually thrown. This lead to a steady lack of information about the origin of the final symptom. As an example, see the following code snippet (extracted from com.arjuna.ats.internal.arjuna.objectstore.JDBCStore.JDBCStore()) ... try { initialise(""); } catch (Exception e) { throw new ObjectStoreError(); } ... Here the original exception "e" is lost in favor of a new ObjectStoreError. No one will never know the cause of the thrown ObjectStoreError, nor see what's wrong without using a debugger (if ever available). Since I saw the binary distribution of JBossTM (at least version 4.5.0) is compiled for Java 1.5, I suppose you aren't denied to use the standard exception chaining mechanism introduced since Java 1.4 (namely the java.lang.Throwable.cause field) Please consider refactoring your code to chain the exception causes. It would be very useful. -- 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

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2010