September 2009 - jbossts-issues - Jboss List Archives

[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

1
3
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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-498) Rename jbosscore.jar

by Mark Little (JIRA)

Rename jbosscore.jar -------------------- Key: JBTM-498 URL: https://jira.jboss.org/jira/browse/JBTM-498 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.5 Reporter: Mark Little Priority: Minor When building the core engine the resultant jar is called jbosscore.jar, which is a little misleading. Maybe jbossts-core.jar? -- 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 month

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-377) XAResourceRecord save/restore state insufficiently paranoid

by Jonathan Halliday (JIRA)

XAResourceRecord save/restore state insufficiently paranoid ----------------------------------------------------------- Key: JBTM-377 URL: http://jira.jboss.com/jira/browse/JBTM-377 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Fix For: 4.4.CR2 The XAResourceRecord save state method writes meta-data into the objectstore before attempting to Serialize and write the actual bytes for an XAResource that it believes, on the basis of it implementing the market interface, is Serializable. If the serialization fails at runtime, the objectstore record is left in an invalid state and can cause the recovery pass to blow up in horrible ways. We should obtain the byte[] representing the serialized resource before writing anything to the record so that this does not occur. If serialization fails, the record will therefore be useless but at least not otherwise broken. -- 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, 2 months

2
10
0 / 0

[JBoss JIRA] Created: (JBTM-608) Allow synchronization registration as long as beforeCompletion phase not finished

by Mark Little (JIRA)

Allow synchronization registration as long as beforeCompletion phase not finished --------------------------------------------------------------------------------- Key: JBTM-608 URL: https://jira.jboss.org/jira/browse/JBTM-608 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA, JTS, Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: future There are some edge cases where this may be 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-583) Go through deprecated methods etc. and prune

by Mark Little (JIRA)

Go through deprecated methods etc. and prune -------------------------------------------- Key: JBTM-583 URL: https://jira.jboss.org/jira/browse/JBTM-583 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.7.0 Reporter: Mark Little Assignee: Mark Little Fix For: future We have a lot that have been deprecated for years. Time to prune. -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-229) Configurable exception throwing for multi-threaded environment

by Mark Little (JIRA)

Configurable exception throwing for multi-threaded environment -------------------------------------------------------------- Key: JBTM-229 URL: http://jira.jboss.com/jira/browse/JBTM-229 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Reporter: Mark Little Assigned To: Mark Little Priority: Optional Currently if a thread A terminates a transaction in the same way as a thread B subsequently tries to, B will get an exception. This is to allow B to differentiate between it successfully terminating the transaction and someone else doing so. This comes from the OTS heritage. Maybe we should make it configurable, so deployments that couldn't care, can turn off that capability. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-571) AppServerJDBCXARecovery does not support encrypted datasource passwords

by Matt Davis (JIRA)

AppServerJDBCXARecovery does not support encrypted datasource passwords ----------------------------------------------------------------------- Key: JBTM-571 URL: https://jira.jboss.org/jira/browse/JBTM-571 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.6.1 Reporter: Matt Davis This is a request for encrypted datasource password support in the AppServerJDBCXARecovery plugin. -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-605) subordinate tx core commit fails are not passed to JTA layer

by Jonathan Halliday (JIRA)

subordinate tx core commit fails are not passed to JTA layer ------------------------------------------------------------ Key: JBTM-605 URL: https://jira.jboss.org/jira/browse/JBTM-605 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Mark Little Fix For: 4.8.0 Where commit on an XAResourceRecord fails in such as way as to return TwoPhaseOutcome.FINISH_ERROR, no error is seen at the JTA (actually JCA XATerminator) layer, effectively making the commit failure invisible except by reading the WARN in the log files. Core does not consider this situation a heuristic, as with a single record there is no inconsistency as such. However, to a user it is an error - they asked for a commit but got a rollback. -- 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
11
0 / 0

[JBoss JIRA] Created: (JBTM-390) add ability to run DTF tests locally without DTF server

by Jonathan Halliday (JIRA)

add ability to run DTF tests locally without DTF server ------------------------------------------------------- Key: JBTM-390 URL: https://jira.jboss.org/jira/browse/JBTM-390 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Release Process, Testing Affects Versions: 4.4.CR1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.4.CR2 JBossTS has a substantial investment in DTF tests. However, running these is a complex process, involving building and deploying to a pre-configured DTF instance or installing the DTF locally on the developer's workstation, including tomcat, mysql etc. Now the DTF is open source and the tests are likewise in the public repository, it would be nice for developers to be able to run them with less hassle, much like unit tests. This issue is tightly integrated with DTF-4, which covers provision of the necessary functionality in DTF. -- 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
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2009