August 2008 - jbossts-issues - Jboss List Archives

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

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-252) Documentation: left align paragraphs to remove extra spacing

by Daniel Bevenius (JIRA)

Documentation: left align paragraphs to remove extra spacing ------------------------------------------------------------ Key: JBTM-252 URL: http://jira.jboss.com/jira/browse/JBTM-252 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Trivial Some of the docs (maybe all) have paragraphs which are not left aligned which is causing extra spacing between words. Simply making the paragraphs left aligned will rectify this. Thanks, Daniel -- 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, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBTM-228) Check that endSuspendedRMs called if transaction times out

by Mark Little (JIRA)

Check that endSuspendedRMs called if transaction times out ---------------------------------------------------------- Key: JBTM-228 URL: http://jira.jboss.com/jira/browse/JBTM-228 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-366) integrate heuristics resolution tool with AS 5.0

by Jonathan Halliday (JIRA)

integrate heuristics resolution tool with AS 5.0 ------------------------------------------------ Key: JBTM-366 URL: http://jira.jboss.com/jira/browse/JBTM-366 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Application Server Integration, Recovery, Tooling Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Fix For: 4.6 The existing object store browser runs as a standalone process and is present only in the full TS distribution. We should have a subset of this functionality integrated with AS 5.0, so that app server users can view and cleanup tx. Ideally this should integrate seamlessly with the rest of the AS tooling e.g. console integration. The prototyping Maciej did to make the existing objectstore browser runnable from the browser in AS 4.x is a step in the right direction. However, we can't really decide how this should work until the final state of the tooling for AS 5.0 becomes clear. This may therefore follow in a point release after 5.0. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-389) TransactionStatusManager and Recovery integration without Sockets

by Dmitri Voronov (JIRA)

TransactionStatusManager and Recovery integration without Sockets ----------------------------------------------------------------- Key: JBTM-389 URL: https://jira.jboss.org/jira/browse/JBTM-389 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.2.3 Environment: JBoss 4.2.3 Reporter: Dmitri Voronov Attachments: jboss-jta-without-sockets.zip In the current JBoss integration the communication within arjuna occurs over Sockets whereby the communication is within the same JVM and doesn't need to use any socket or listen on any ports. This requires a configuration overhead, if the ports should be determined. If no ports have been configured, the next free port is opened. In our environment we manage the port ranges per JBoss instance, e.g. https, rmi etc. My suggestion is to use piped streams (see attachment) ; it would prevent the changes on Arjuna's API and the internal algorithms. -- 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, 7 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 August 2008