November 2007 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-240) Add Spring configuration to documentation

by Mark Little (JIRA)

Add Spring configuration to documentation ----------------------------------------- Key: JBTM-240 URL: http://jira.jboss.com/jira/browse/JBTM-240 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Jonathan Halliday Fix For: 4.4 We should add this http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossTransactionsWithSpring to the shipped docs. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-304) Update the management MBean with all of the collected statistics

by Mark Little (JIRA)

Update the management MBean with all of the collected statistics ---------------------------------------------------------------- Key: JBTM-304 URL: http://jira.jboss.com/jira/browse/JBTM-304 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Reporter: Mark Little Assigned To: Andrew Dinn Priority: Minor JBossTS collects more information than the MBean now exposes. -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-289) remove use of Synchronizations for lock storage in jboss integration

by Jonathan Halliday (JIRA)

remove use of Synchronizations for lock storage in jboss integration -------------------------------------------------------------------- Key: JBTM-289 URL: http://jira.jboss.com/jira/browse/JBTM-289 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.2.3.SP6 JBossAS needs to be able to lock transactions regardless of their state. Since the current integration implementation uses Synchronizations to store lock state, locking is possible only during transactions lifecycle phases where Synchronization registration is permitted. Relax this by changing the integration so that locks are stored using the general object storage mechanism added to TransactionImple to support JTA 1.1. -- 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

1
6
0 / 0

[JBoss JIRA] Created: (JBTM-279) Find the JBossMQ recovery code and make sure it's shipped in the next release of AS.

by Mark Little (JIRA)

Find the JBossMQ recovery code and make sure it's shipped in the next release of AS. ------------------------------------------------------------------------------------ Key: JBTM-279 URL: http://jira.jboss.com/jira/browse/JBTM-279 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: Jonathan Halliday Priority: Blocker Adrian did some work on providing a ResourceRecovery implementation and RecoveryModule for JBossMQ (for Glencore). I had assumed that support would make sure it was shipped in subsequent releases of AS (since recovery is pretty important), but that doesn't seem to be the case. If they are not going to do it, then we need to because MQ is effectively frozen (at least that's what Adrian thought). -- 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, 12 months

4
8
0 / 0

[JBoss JIRA] Created: (JBTM-253) Listen address of JBossTS ports not configurable

by Arto Huusko (JIRA)

Listen address of JBossTS ports not configurable ------------------------------------------------ Key: JBTM-253 URL: http://jira.jboss.com/jira/browse/JBTM-253 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP3 Environment: JBoss AS 4.2.0 GA Reporter: Arto Huusko Assigned To: Mark Little JBossTS integrated in JBoss AS 4.2.0 GA always binds some tcp ports to listen on all addresses. jboss.bind.address has no effect on the listen address, nor is it otherwise configurable. Looking at source code (for example ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/TransactionStatusManager.java in jbossts-jta-4.2.3.SP3-src.zip) confirms that there is no kind of support for binding the listen address, only the port can be freely selected. The listen address should be configurable, so that it can be limited to localhost, for example. In addition, if possible, it would be nice to be able to disable listening on any ports. I'm not sure if the TransactionStatusManager really needs to listen on any port in a simple JBoss AS installation. -- 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

16 years

4
10
0 / 0

[JBoss JIRA] Created: (JBTM-274) JBossWorkManager converts from seconds to milliseconds

by Mark Little (JIRA)

JBossWorkManager converts from seconds to milliseconds ------------------------------------------------------ Key: JBTM-274 URL: http://jira.jboss.com/jira/browse/JBTM-274 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.2.3.SP6 Transaction timeouts on the work manager were assumed to be in seconds. JBossWorkManager is converting them to milliseconds before we get the timeout. We then convert them to milliseconds (under the assumption they were defined in seconds). -- 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

16 years, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (JBTM-278) XAResource.end error may not cause rollback

by Jonathan Halliday (JIRA)

XAResource.end error may not cause rollback ------------------------------------------- Key: JBTM-278 URL: http://jira.jboss.com/jira/browse/JBTM-278 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.3.SP5 Reporter: Jonathan Halliday Assigned To: Mark Little Fix For: 4.4 An XAResource.end call may return an XA_RB* error. In such case, the resource should (but currently does not) still get rollback called on it too. Update XAResourceRecord.java to fix. -- 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

16 years, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (JBTM-288) Add suspend/resume to recovery manager

by Mark Little (JIRA)

Add suspend/resume to recovery manager -------------------------------------- Key: JBTM-288 URL: http://jira.jboss.com/jira/browse/JBTM-288 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 Start/Stop are really termination states. No way to restart a recovery manager once it is stopped. -- 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

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-291) Change default timeout mechanism from NORMAL to DYNAMIC.

by Mark Little (JIRA)

Change default timeout mechanism from NORMAL to DYNAMIC. -------------------------------------------------------- Key: JBTM-291 URL: http://jira.jboss.com/jira/browse/JBTM-291 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Andrew Dinn Fix For: 4.4 MR1 -- 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

16 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-307) Update xa_prepare handling for rm/err failures in light of modern RMs

by Mark Little (JIRA)

Update xa_prepare handling for rm/err failures in light of modern RMs --------------------------------------------------------------------- Key: JBTM-307 URL: http://jira.jboss.com/jira/browse/JBTM-307 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP6 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 Initial RM implementations of XAResources that threw RMERR/RMFAIL on prepare didn't honour the XA spec, so TS had to assume heuristic outcome. That's no longer the case (probably hasn't been for many years). We can/should remove that option in the codebase. -- 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

16 years, 1 month

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2007