August 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-334) deprecate NORMAL mode reaper

by Jonathan Halliday (JIRA)

deprecate NORMAL mode reaper ---------------------------- Key: JBTM-334 URL: http://jira.jboss.com/jira/browse/JBTM-334 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3.0.BETA2 Reporter: Jonathan Halliday Fix For: 4.4 It is misleading to have DYNAMIC be the default whilst NORMAL still exists. Deprecate NORMAL, replacing it with equivalent PERIODIC. Make DYNAMIC the default in properties file and code. -- 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-384) InactiveTransactionException update was incorrectly removed.

by Mark Little (JIRA)

InactiveTransactionException update was incorrectly removed. ------------------------------------------------------------ Key: JBTM-384 URL: http://jira.jboss.com/jira/browse/JBTM-384 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Affects Versions: 4.4.CR1 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-255) do more testing of reaper worker thread

by Andrew Dinn (JIRA)

do more testing of reaper worker thread --------------------------------------- Key: JBTM-255 URL: http://jira.jboss.com/jira/browse/JBTM-255 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.2.3.SP5 Reporter: Andrew Dinn Assigned To: Andrew Dinn Fix For: 4.4 Need to extend unit test to check zombie exit and als to add stress test for reaper performance assessment -- 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-395) performance comparison with other OSS TMs

by Jonathan Halliday (JIRA)

performance comparison with other OSS TMs ----------------------------------------- Key: JBTM-395 URL: https://jira.jboss.org/jira/browse/JBTM-395 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, Testing Affects Versions: 4.4.CR2 Reporter: Jonathan Halliday Assignee: Michael Musgrove Fix For: 4.4.0.GA Compare JTA performance against competing products with common XA resource managers and config options. Profile to identify any particular bottlenecks. JOTM, Atomikos, Bitronix, Simple JTA. -- 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

16 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-353) XAResourceRecovery has wrong conceptual model

by Jonathan Halliday (JIRA)

XAResourceRecovery has wrong conceptual model --------------------------------------------- Key: JBTM-353 URL: http://jira.jboss.com/jira/browse/JBTM-353 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.4.CR1 XAResourceRecovery is based on an iterator model: public boolean initialise (String p) throws SQLException; public boolean hasMoreResources (); public XAResource getXAResource () throws SQLException; However, XAResourceRecovery instances are created once at recovery manager startup. This means there is only ever one recovery pass that actually returns resources. On later passes the iterator is exhausted and returns nothing. This is the wrong model. XAResources are not individual entities in need of recovery. Rather they are entities from which a list of Xids in need of recovery can be retrieved. If the configuration of the underlying system does not change, the set of XAResources should remain constant over time, being one per known resource manager. On each recovery pass the list of in-doubt Xids returned by a recover scan on that resource many change. The model should change to follow that used by JCA ResourceAdapter: public XAResource[] getXAResources() The recovery pass would then obtain and walk the array rather than using the current iterator model. Additionally the exception types should be more generic. SQLException assumes the resource manager is a db, which may not be the case. This will also impact the recovery examples, which implement this interface. -- 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, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBTM-383) doc updates for 4.4 release

by Jonathan Halliday (JIRA)

doc updates for 4.4 release --------------------------- Key: JBTM-383 URL: http://jira.jboss.com/jira/browse/JBTM-383 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4.CR1 Reporter: Jonathan Halliday Assigned To: Jonathan Halliday Fix For: 4.4.CR2 Update documentation set and trailmap for the 4.4 release. -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-394) support JBossAS 5.0 service binding manager

by Jonathan Halliday (JIRA)

support JBossAS 5.0 service binding manager ------------------------------------------- Key: JBTM-394 URL: https://jira.jboss.org/jira/browse/JBTM-394 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jonathan Halliday When deployed in JBossAS, the JTA and JTS should take their IP and port binding information from the app server's Service Binding Manager rather than the jbossjta|jbossjts-properties.xml files. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=140667 http://wiki.jboss.org/wiki/AS5ServiceBindingManager -- 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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-358) Update documentation to describe support for OASIS 1.1 WSTX protocols

by Andrew Dinn (JIRA)

Update documentation to describe support for OASIS 1.1 WSTX protocols --------------------------------------------------------------------- Key: JBTM-358 URL: http://jira.jboss.com/jira/browse/JBTM-358 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, Documentation Affects Versions: 4.3.0.GA Reporter: Andrew Dinn Assigned To: Andrew Dinn Fix For: 4.4.CR1 This being raised to allow JBTM-37 (which includes all the required code changes) to be closed. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-393) Clarify use of Business Agreement GetStatus and Status messages and relation to BAParticipant interface

by Andrew Dinn (JIRA)

Clarify use of Business Agreement GetStatus and Status messages and relation to BAParticipant interface ------------------------------------------------------------------------------------------------------- Key: JBTM-393 URL: https://jira.jboss.org/jira/browse/JBTM-393 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.4.CR1 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.4 The BAWithXXXCompletionParticipant interfaces which define the API implemented by Web service-specific participant implementations (and also the participant stubs on the coordinator side) include methods with the following signatures: public String status() throws SystemException; public String unknown() throws SystemException; public String error() throws SystemException; These appear to relate (vaguely) to the BA protocol message pair GetStatus (request) and Status (response) which can be initiated from either the coordinator or the participant. If so then they appear to be inappropriate as part of the Web service-specific API. The application does not and, indeed, should not need to know about the state model employed by the protocol implementation. status() probably ought to be dropped and maybe also the other two. However, it may be that error and unknown are intended to be called during recovery processing or,perhaps, even normal processing (e.g. if the participant receives an InvalidState fault or a Failed message). So, this needs to be clarified first. The message handlers for the i) GetStatus and ii) Status messages are currently implemented, respectively, i) to dispatch a Status message with the current (service or coordinator-side) participant engine state and ii) to do nothing. The current implementation does not ever dispatch a GetStatus message -- it was not necessary to do so for the purpose of implementing recovery on either the coordinatro or the participant side. Since the BA spec provides no details as to when or how these messages are to be used the current implementation is, perhaps, appropriate, This needs to be clarified and, if necessary, the code modified to verify its use. -- 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

16 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-402) Spurious character after comment in PropagationContextManager

by Mark Little (JIRA)

Spurious character after comment in PropagationContextManager ------------------------------------------------------------- Key: JBTM-402 URL: https://jira.jboss.org/jira/browse/JBTM-402 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.4.CR1 Reporter: Mark Little Assignee: Mark Little Fix For: 4.4.CR2 'e' appeared when fixing JBTM-330. -- 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

16 years, 3 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 August 2008