September 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-366) integrate heuristics resolution tool with AS 5.0

by Jonathan Halliday (JIRA)

integrate heuristics resolution tool with AS 5.0 ------------------------------------------------ Key: JBTM-366 URL: http://jira.jboss.com/jira/browse/JBTM-366 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Application Server Integration, Recovery, Tooling Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Fix For: 4.6 The existing object store browser runs as a standalone process and is present only in the full TS distribution. We should have a subset of this functionality integrated with AS 5.0, so that app server users can view and cleanup tx. Ideally this should integrate seamlessly with the rest of the AS tooling e.g. console integration. The prototyping Maciej did to make the existing objectstore browser runnable from the browser in AS 4.x is a step in the right direction. However, we can't really decide how this should work until the final state of the tooling for AS 5.0 becomes clear. This may therefore follow in a point release after 5.0. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBTM-389) TransactionStatusManager and Recovery integration without Sockets

by Dmitri Voronov (JIRA)

TransactionStatusManager and Recovery integration without Sockets ----------------------------------------------------------------- Key: JBTM-389 URL: https://jira.jboss.org/jira/browse/JBTM-389 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.2.3 Environment: JBoss 4.2.3 Reporter: Dmitri Voronov Attachments: jboss-jta-without-sockets.zip In the current JBoss integration the communication within arjuna occurs over Sockets whereby the communication is within the same JVM and doesn't need to use any socket or listen on any ports. This requires a configuration overhead, if the ports should be determined. If no ports have been configured, the next free port is opened. In our environment we manage the port ranges per JBoss instance, e.g. https, rmi etc. My suggestion is to use piped streams (see attachment) ; it would prevent the changes on Arjuna's API and the internal algorithms. -- 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, 1 month

2
7
0 / 0

[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] Updated: (JBTM-48) Move tools to Eclipse?

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-48?page=com.atlassian.jira.plugin... ] Jonathan Halliday updated JBTM-48: ---------------------------------- Fix Version/s: 4.6 (was: 4.4.0.GA) > Move tools to Eclipse? > ---------------------- > > Key: JBTM-48 > URL: https://jira.jboss.org/jira/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: 4.6 > > > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 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 September 2008