October 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-398) Compile list of refactor/consolidation options with existing code.

by Mark Little (JIRA)

Compile list of refactor/consolidation options with existing code. ------------------------------------------------------------------ Key: JBTM-398 URL: https://jira.jboss.org/jira/browse/JBTM-398 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation, Transaction Core, WS-T Implementation Reporter: Mark Little Assignee: 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-618) Reduce synchronization boundaries on LockManager.setlock

by Mark Little (JIRA)

Reduce synchronization boundaries on LockManager.setlock -------------------------------------------------------- Key: JBTM-618 URL: https://jira.jboss.org/jira/browse/JBTM-618 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.CP06 Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.0 Currently too coarse grained. -- 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

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-528) Periodic commit retry

by Mark Little (JIRA)

Periodic commit retry --------------------- Key: JBTM-528 URL: https://jira.jboss.org/jira/browse/JBTM-528 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.0 XA_RETRY on commit ... /* * Could do timeout retry here, but that could cause other resources in the list to go down the * heuristic path (some are far too keen to do this). Fail and let recovery retry. Meanwhile * the coordinator will continue to commit the other resources immediately. */ -- 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

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-251) Check conformance and compatibility of two JTA implementations

by Mark Little (JIRA)

Check conformance and compatibility of two JTA implementations -------------------------------------------------------------- Key: JBTM-251 URL: http://jira.jboss.com/jira/browse/JBTM-251 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: Andrew Dinn Make sure that both of our JTA implementations behave as similarly as possible from an interface perspective. For example, that timeouts are handled the same. Some differences are bound to be visible because the two implementations have different capabilities. But ignoring those, we need to be as consistent as possible. -- 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

14 years, 1 month

4
9
0 / 0

[JBoss JIRA] Updated: (JBTM-112) Add QA tests to check default timeout behaviour

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/browse/JBTM-112?page=com.atlassian.jira.plugin.sys... ] Jonathan Halliday updated JBTM-112: ----------------------------------- Assignee: Jonathan Halliday (was: Mark Little) Fix Version/s: 4.15.0 (was: 5.0.0) > Add QA tests to check default timeout behaviour > ----------------------------------------------- > > Key: JBTM-112 > URL: https://jira.jboss.org/browse/JBTM-112 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assignee: Jonathan Halliday > Fix For: 4.15.0 > > -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-801) SoapFault service is using network URL for sioap envelope WSDL which can cause recovery failure

by Andrew Dinn (JIRA)

SoapFault service is using network URL for sioap envelope WSDL which can cause recovery failure ----------------------------------------------------------------------------------------------- Key: JBTM-801 URL: https://jira.jboss.org/browse/JBTM-801 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.6.1.CP08 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.6.1.CP09 The soapfault wsdl used by the XTS SoapFaultService is importing the soap envelope wsdl via a network URL. Ideally the wsdl shoudl be retrieved form a local copy. This ha sbeen fixed in trunk but needs backporting to the EAP 5 branch. -- 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

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-793) update docs for 4.13

by Jonathan Halliday (JIRA)

update docs for 4.13 -------------------- Key: JBTM-793 URL: https://jira.jboss.org/browse/JBTM-793 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.13.0 Begin replacement of .odt with docbook, including consequent changes to build system. -- 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

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-781) Document configuration fo XTS via jboss-beans.xml or xts-properties.xml

by Andrew Dinn (JIRA)

Document configuration fo XTS via jboss-beans.xml or xts-properties.xml ----------------------------------------------------------------------- Key: JBTM-781 URL: https://jira.jboss.org/browse/JBTM-781 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, XTS Affects Versions: 4.12.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.13.0 New bean injection/property manager config needs to be documented -- 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

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-794) TransactionReaper may execute continuously

by Kevin Conner (JIRA)

TransactionReaper may execute continuously ------------------------------------------ Key: JBTM-794 URL: https://jira.jboss.org/browse/JBTM-794 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.6.1.CP07 Reporter: Kevin Conner JBossTS TransactionReaper contains a bug which results in the reaper executing continuously within dynamic mode, rather than pausing between runs. The ReaperThread calls the TransactionReaper.checkingPeriod() method to determine how long it should pause before it can invoke the TransactionReaper.check() method, however there exists a circumstance where the checkingPeriod() will return a negative period for a sustained time, resulting in the thread executing continuously. This occurs when the check() method is invoked while there are existing transactions in the ReaperElementManager. The check and checkingPeriod methods use the nextDynamicCheckTime variable to store the absolute time at which the next invocation of check should occur, checkingPeriod returns the difference between that time and the current. When the check method is executed after nextDynamicCheckTime has occurred, the method retrieves the first ReaperElement from the ReaperElementManager. The processing continues as follows - if no reaperElement present, reset nextDynamicCheckTime to Long.MAX_VALUE - if present and expired (reaperElement.getAbsoluteTimeout() <= now) then the element is processed - if present and not expired (reaperElement.getAbsoluteTimeout() > now) then do nothing. It is the last behaviour which is incorrect as the nextDynamicCheckTime still refers to the previous absolute timeout, i.e. < now, resulting in all calls to checkinPeriod() returning a negative value. This will only be halted if one of the other conditions is true, i.e. the ReaperElementManager is empty or the head element must be processed by this thread. -- 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

14 years, 1 month

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2010