October 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-347) Make sure XTS works with HTTPS

by Mark Little (JIRA)

Make sure XTS works with HTTPS ------------------------------ Key: JBTM-347 URL: http://jira.jboss.com/jira/browse/JBTM-347 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Reporter: Mark Little Assigned To: Andrew Dinn Priority: Critical Fix For: 4.4 WS-TX 1.1 recommended (though did not mandate) HTTPS for the "transport". For interoperability, HTTPS cannot be mandated, but some implementations (e.g., MSFT) don't have an "off switch" and won't work unless HTTPS is used. Yes, this breaks interoperability, but it's unlikely to change. We need to make sure that we can work successfully with HTTPS and MSFT. -- 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

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-369) String property replacement in configuration

by Dmitri Voronov (JIRA)

String property replacement in configuration -------------------------------------------- Key: JBTM-369 URL: http://jira.jboss.com/jira/browse/JBTM-369 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.3.0.GA Reporter: Dmitri Voronov Please implement string property replacement in jbossjta-properties.xml like: <property name="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="${my.unique.name}"/> -- 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

15 years, 3 months

5
14
0 / 0

[JBoss JIRA] Created: (JBTM-405) PropertyManagerImpl.getPropertyFromSubTree(String name) looks for properties in _parentPropertyManagers and not in _childPropertyManagers

by Dmitri Voronov (JIRA)

PropertyManagerImpl.getPropertyFromSubTree(String name) looks for properties in _parentPropertyManagers and not in _childPropertyManagers ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-405 URL: https://jira.jboss.org/jira/browse/JBTM-405 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.0.GA Environment: JBoss-4.2.3.GA Reporter: Dmitri Voronov PropertyManagerImpl.getPropertyFromSubTree(String name) looks for properties in _parentPropertyManagers and not in _childPropertyManagers So the call: String tsmPortStr = arjPropertyManager.propertyManager.getProperty("com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort" ) ; from com.arjuna.ats.arjuna.recovery.TransactionStatusManager misses, whereby the property exists in a child property manager. -- 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

15 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-420) add in-memory (i.e. Volatile) ObjectStore impl.

by Jonathan Halliday (JIRA)

add in-memory (i.e. Volatile) ObjectStore impl. ----------------------------------------------- Key: JBTM-420 URL: https://jira.jboss.org/jira/browse/JBTM-420 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing, Transaction Core Affects Versions: 4.4.0.GA Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.5 For performance testing purposes it would be nice to have a pure in-memory objectstore implementation. This would store object states in the JVM's RAM and thus facilitate comparisons: - comparing driving XAResources directly from the application code vs. via JBossTS would give the overhead of the transaction manager code without any i/o overhead i.e. tell us how performant the transaction manager's 'business logic' is and what the maximum theoretical throughput is if the persistent storage is not a bottleneck. Could also be useful when stress testing or profiling the rest of the transaction manager code. - comparing against any other ObjectStore provides figures that show exactly what performance impact that store has i.e. it provides a baseline for evaluating other stores. Previously it's only been possible to compare any given store impl against driving XA resources directly, which does not account for the overhead of the transaction manager code. Naturally there's no crash recovery support, so it's totally unsuitable for production usage. -- 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

15 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-403) Check OTS TransactionFactory is exported through app server

by Mark Little (JIRA)

Check OTS TransactionFactory is exported through app server ----------------------------------------------------------- Key: JBTM-403 URL: https://jira.jboss.org/jira/browse/JBTM-403 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTS Implementation Reporter: Mark Little Assignee: Mark Little -- 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

15 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-417) Merge object store changes from transition period

by Mark Little (JIRA)

Merge object store changes from transition period ------------------------------------------------- Key: JBTM-417 URL: https://jira.jboss.org/jira/browse/JBTM-417 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: 4.6 There are some changes to the code (at least the object store code) that were being made while we were putting the main branch into svn. These updates need to be added in now. -- 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

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-318) Update recovery wiki page

by Mark Little (JIRA)

Update recovery wiki page ------------------------- Key: JBTM-318 URL: http://jira.jboss.com/jira/browse/JBTM-318 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, JTA Implementation, Recovery Reporter: Mark Little Assigned To: 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-243) Subordinate coordinator misses cleanup

by Mark Little (JIRA)

Subordinate coordinator misses cleanup -------------------------------------- Key: JBTM-243 URL: http://jira.jboss.com/jira/browse/JBTM-243 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 -- 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

15 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-256) TransactionImple::endSuspendedRMs may dive out before ending all XAResources

by Andrew Dinn (JIRA)

TransactionImple::endSuspendedRMs may dive out before ending all XAResources ---------------------------------------------------------------------------- Key: JBTM-256 URL: http://jira.jboss.com/jira/browse/JBTM-256 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Affects Versions: 4.2.3.SP5 Reporter: Andrew Dinn Assigned To: Andrew Dinn Fix For: 4.4 TransactionImple::endSuspendedRMs loops through all enlisted XAResources sending them an end() as a precursor to commit or rollback. It is supposed to notify all resources even if one (or more) of them throws an exception, returning true iff they all complete. As currently coded it returns failure at the first exception, potentially omitting some of the end() calls. -- 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

15 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-295) Identify redundant finalize methods on classes employed by the JTS implementation and remove them.

by Andrew Dinn (JIRA)

Identify redundant finalize methods on classes employed by the JTS implementation and remove them. -------------------------------------------------------------------------------------------------- Key: JBTM-295 URL: http://jira.jboss.com/jira/browse/JBTM-295 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.2.3 Reporter: Andrew Dinn Assigned To: Andrew Dinn Fix For: 4.4 Identify redundant finalize methods in classes employed by the JTS which are adversely affecting GC performance and remove them, documenting any effect this may have in the relevant release notes. -- 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

15 years, 4 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 October 2008