jbossts-issues July 2009

jbossts-issues@lists.jboss.org

1 participants
113 discussions

[JBoss JIRA] Created: (JBTM-235) Check thread creation for context inheritance

by Kevin Conner (JIRA)

Check thread creation for context inheritance --------------------------------------------- Key: JBTM-235 URL: http://jira.jboss.com/jira/browse/JBTM-235 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Mark Little All threads created in the transaction manager should be checked to make sure they are not inheriting anything unexpected (classloader/thread locals etc) -- 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, 6 months

4
9
0 / 0

[JBoss JIRA] Created: (JBTM-503) Shutdown the ExpiredEntryMonitor when stopping the RecoveryManager

by Mauro Molinari (JIRA)

Shutdown the ExpiredEntryMonitor when stopping the RecoveryManager ------------------------------------------------------------------ Key: JBTM-503 URL: https://jira.jboss.org/jira/browse/JBTM-503 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.5 Environment: Tomcat + Spring + DBCP + JBossJTA Reporter: Mauro Molinari When the recovery manager is started, the implementation RecoveryManagerImple starts the ExpiredEntryMonitor. When you stop the recovery manager, however, the ExpiredEntryMonitor is not shut down. On line 250 of com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple there's the line ExpiredEntryMonitor.shutdown() commented out, with a "TODO why?" comment immediately before. I don't know exactly what should be the lifecylce of ExpiredEntryMonitor versus that of RecoveryManagerImple, however I think that one of the following should happen: - ExpiredEntryMonitor is started when RecoveryManagerImple is started (rather than constructed), so that it is shut down when the RecoveryManagerImple is stopped OTHERWISE - RecoveryManagerImple provides a way to "dispose" or "disable" it and this includes the shutdown of ExpiredEntryMonitor OTHERWISE - it is documented that stopping the recovery manager needs the ExpiredEntryMonitor to be stopped too: however, please consider that com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.shutdown() throws a NullPointerException if called while the ExpiredEntryMonitor has not been started before and there is no public method to test if it has been started or not; so if I need to write some code that stops the ExpiredEntryMonitor (without knowing if it has been started or not) I have to write some ugly code like: {code:java} try { ExpiredEntryMonitor.shutdown(); } catch(final NullPointerException e) { // ExpiredEntryMonitor had not been started } {code} -- 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, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (JBTM-569) Transaction/Recovery Manager threads need to be able to be started and stopped cleanly whether running in JBossAS, embedded in an APP or standalone

by Andrew Dinn (JIRA)

Transaction/Recovery Manager threads need to be able to be started and stopped cleanly whether running in JBossAS, embedded in an APP or standalone --------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-569 URL: https://jira.jboss.org/jira/browse/JBTM-569 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.7.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.8.0 -- 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, 6 months

1
1
0 / 0

← Newer
1
...
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2009