November 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-409) WS-BA coordinator interposition support

by Jonathan Halliday (JIRA)

WS-BA coordinator interposition support --------------------------------------- Key: JBTM-409 URL: https://jira.jboss.org/jira/browse/JBTM-409 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4.0.GA Reporter: Jonathan Halliday Assignee: Andrew Dinn 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

15 years, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (JBTM-315) Fix labs text

by Mark Little (JIRA)

Fix labs text ------------- Key: JBTM-315 URL: http://jira.jboss.com/jira/browse/JBTM-315 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.3.0.BETA2 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial "JBoss Transactions is founded on industry proven technology and an 18 year history as a leader in distributed transactions." Was true 2 years ago. Needs to say 20+ now. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-283) Make sure JDBC text is clear that it should only be used outside of application servers

by Mark Little (JIRA)

Make sure JDBC text is clear that it should only be used outside of application servers --------------------------------------------------------------------------------------- Key: JBTM-283 URL: http://jira.jboss.com/jira/browse/JBTM-283 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-332) Make sure it is clear that JBossTS can be used outside of an application server

by Mark Little (JIRA)

Make sure it is clear that JBossTS can be used outside of an application server ------------------------------------------------------------------------------- Key: JBTM-332 URL: http://jira.jboss.com/jira/browse/JBTM-332 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Mark Little -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-397) Pull higher-performance transaction log implementation across from backup

by Mark Little (JIRA)

Pull higher-performance transaction log implementation across from backup ------------------------------------------------------------------------- Key: JBTM-397 URL: https://jira.jboss.org/jira/browse/JBTM-397 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core 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

15 years, 10 months

1
4
0 / 0

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

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2008