November 2008 - jbossts-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (JBTM-434) PeriodicRecovery thread needs to marked as daemon thread.

by Ramesh Reddy (JIRA)

PeriodicRecovery thread needs to marked as daemon thread. --------------------------------------------------------- Key: JBTM-434 URL: https://jira.jboss.org/jira/browse/JBTM-434 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.0.GA Reporter: Ramesh Reddy Since this is not essential processing thread this needs to marked as daemon, so that when JVM exits, this thread dies gracefully. For detail look at JIRA https://jira.jboss.org/jira/browse/FEDERATE-14 -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-435) Fix docs on OracleXARecovery

by Mark Little (JIRA)

Fix docs on OracleXARecovery ---------------------------- Key: JBTM-435 URL: https://jira.jboss.org/jira/browse/JBTM-435 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Recovery Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-436) Make sure AS integration recovery docs are up-to-date

by Mark Little (JIRA)

Make sure AS integration recovery docs are up-to-date ----------------------------------------------------- Key: JBTM-436 URL: https://jira.jboss.org/jira/browse/JBTM-436 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration, Documentation, Recovery Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-404) Add Recovery for Business Activities

by Andrew Dinn (JIRA)

Add Recovery for Business Activities ------------------------------------ Key: JBTM-404 URL: https://jira.jboss.org/jira/browse/JBTM-404 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.4.CR1 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.6 The XTS WS-BA implementation needs to implement coordinator and participant recovery -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-426) Disabling read-only optimisation not supported in commit

by Mark Little (JIRA)

Disabling read-only optimisation not supported in commit -------------------------------------------------------- Key: JBTM-426 URL: https://jira.jboss.org/jira/browse/JBTM-426 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: 4.5 We allow the readonly optimisation to be disabled at runtime. However, this only works for rollback, i.e., a readonly resource still won't get called during commit, but only during abort. This is a bug because it's not what was intended originally. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-424) JTS subordinate transaction checks for interposed synchronization too late

by Mark Little (JIRA)

JTS subordinate transaction checks for interposed synchronization too late -------------------------------------------------------------------------- Key: JBTM-424 URL: https://jira.jboss.org/jira/browse/JBTM-424 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: 4.5 Which means that we will throw an exception if beforeCompletion hasn't been called when in fact we should be calling it in the event no interposed synchronization is being used. -- 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, 5 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 November 2008