October 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-584) Enhance transaction monitoring

by Mark Little (JIRA)

Enhance transaction monitoring ------------------------------ Key: JBTM-584 URL: https://jira.jboss.org/jira/browse/JBTM-584 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: future We now have a listener package to add coordinator specific listeners for different aspects of the lifecycle. -- 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

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-461) Unify timeout-per-thread approach

by Mark Little (JIRA)

Unify timeout-per-thread approach --------------------------------- Key: JBTM-461 URL: https://jira.jboss.org/jira/browse/JBTM-461 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation, Transaction Core, WS-T Implementation Affects Versions: 4.5 Reporter: Mark Little Fix For: 4.7 -- 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

13 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBTM-415) Multi-threaded recovery manager

by Mark Little (JIRA)

Multi-threaded recovery manager ------------------------------- Key: JBTM-415 URL: https://jira.jboss.org/jira/browse/JBTM-415 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4.0.GA Reporter: Mark Little Assignee: Mark Little Fix For: future -- 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

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-302) JTS XA recovery is inconsistent for local JTA XA recovery

by Mark Little (JIRA)

JTS XA recovery is inconsistent for local JTA XA recovery --------------------------------------------------------- Key: JBTM-302 URL: http://jira.jboss.com/jira/browse/JBTM-302 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation, Recovery Reporter: Mark Little Assigned To: Mark Little Fix For: 4.6 It also seems to assume JDBC as a source of XAResources. -- 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

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-263) improve logging robustness

by Jonathan Halliday (JIRA)

improve logging robustness -------------------------- Key: JBTM-263 URL: http://jira.jboss.com/jira/browse/JBTM-263 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.3.SP5 Reporter: Jonathan Halliday Assigned To: Andrew Dinn Priority: Minor Fix For: 4.4 Some @message tags are in normal comments rather than javadoc comments, so they don't get processed into message bundles. Some are missing entirely. It should be possible to develop tooling to detect these at build time by checking against log statements in the code. Also, make the logging more robust in the case where errors are missing - a generic message should be printed in preference to crashing as sometimes happens now. See also JBTM-231. -- 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

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-224) Factor XAResourceRecovery creation out of RecoveryModule

by Mark Little (JIRA)

Factor XAResourceRecovery creation out of RecoveryModule -------------------------------------------------------- Key: JBTM-224 URL: http://jira.jboss.com/jira/browse/JBTM-224 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Affects Versions: 4.2.3.SP4 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

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] Closed: (JBTM-190) lifecycle methods for XA recovery

by Mark Little (JIRA)

[ https://jira.jboss.org/browse/JBTM-190?page=com.atlassian.jira.plugin.sys... ] Mark Little closed JBTM-190. ---------------------------- Resolution: Won't Fix We assume that the XAResourceRecovery instance is responsible for lifecycle and will give new instances when the existing connections are stale (for instance). > lifecycle methods for XA recovery > --------------------------------- > > Key: JBTM-190 > URL: https://jira.jboss.org/browse/JBTM-190 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.2.2 > Reporter: Mark Little > Assignee: Mark Little > Fix For: future > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-99) Fine grained control over setTransactionTimeout execution

by Mark Little (JIRA)

[ https://jira.jboss.org/browse/JBTM-99?page=com.atlassian.jira.plugin.syst... ] Mark Little closed JBTM-99. --------------------------- Resolution: Won't Fix > Fine grained control over setTransactionTimeout execution > --------------------------------------------------------- > > Key: JBTM-99 > URL: https://jira.jboss.org/browse/JBTM-99 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS > Affects Versions: 4.2 > Reporter: Kevin Conner > Assignee: Mark Little > Fix For: future > > > We need to add fine grained control to the transaction timeout handling code. > Areas covered by this include > - transaction inflow > - timeout propagation to resources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBTM-86) Exception chaining

by Mauro Molinari (JIRA)

[ https://jira.jboss.org/browse/JBTM-86?page=com.atlassian.jira.plugin.syst... ] Mauro Molinari commented on JBTM-86: ------------------------------------ Hi Andrew, hi Jonathan, what is the fix version that includes the whole fix? 4.14? Thanks in advance! > Exception chaining > ------------------ > > Key: JBTM-86 > URL: https://jira.jboss.org/browse/JBTM-86 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA, JTS > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Andrew Dinn > Priority: Optional > > Look at the feasibility of chaining exceptions in a distributed transaction to preseve error information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-48) Move tools to Eclipse?

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/browse/JBTM-48?page=com.atlassian.jira.plugin.syst... ] Jonathan Halliday closed JBTM-48. --------------------------------- Resolution: Won't Fix > Move tools to Eclipse? > ---------------------- > > Key: JBTM-48 > URL: https://jira.jboss.org/browse/JBTM-48 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.2 > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > Fix For: future > > > Currently we have a set of management tools that use their own graphical interfaces (jgraph I think). Do we maintain these, or move them all to run within Eclipse? It seems that Eclipse is the way to go for any development tools, but I'm not convinced about run-time management tools. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2010