June 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-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-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-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-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-326) TxImporter is not thread-safe and it is used concurrent environment

by Pavel Kadlec (JIRA)

TxImporter is not thread-safe and it is used concurrent environment ------------------------------------------------------------------- Key: JBTM-326 URL: http://jira.jboss.com/jira/browse/JBTM-326 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP7 Environment: JBoss-4.2.1.GA Reporter: Pavel Kadlec TxImporter is used by com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple. The field TxImporter._transactions is static and there can be more XATerminatorImple objects in JVM or there can more threads in one XATerminatorImple object. The access to that field is not synchronized. Type of the field is non-synchronized HashMap. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-330) PropagationContextManager.getTransactionPropagationContext() to log returned tpc

by Galder Zamarreno (JIRA)

PropagationContextManager.getTransactionPropagationContext() to log returned tpc -------------------------------------------------------------------------------- Key: JBTM-330 URL: http://jira.jboss.com/jira/browse/JBTM-330 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3.0.BETA2, 4.2.3.SP6 Reporter: Galder Zamarreno >From a support point of view, it'd be really helpful if the JTA and JTS PropagationContextManager logged which tcp is returned when getTransactionPropagationContext() is called. I have done a local patch for the JTA version as a result of trying to figure out how it worked internally: public Object getTransactionPropagationContext() { if (log.isDebugEnabled()) { log.debug("PropagationContextManager.getTransactionPropagationContext - called"); } String txid = ((BasicAction.Current() == null) ? null : BasicAction.Current().get_uid().stringForm()); if (log.isDebugEnabled()) { log.debug("PropagationContextManager.getTransactionPropagationContext - returned tpc = " + txid); } return txid; } If everyone's happy with this, I can commit it myself. Thoughts? -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-287) 1PC mentioned in XTS docs

by Mark Little (JIRA)

1PC mentioned in XTS docs ------------------------- Key: JBTM-287 URL: http://jira.jboss.com/jira/browse/JBTM-287 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-280) Convert documents over to OpenOffice format

by Mark Little (JIRA)

Convert documents over to OpenOffice format ------------------------------------------- Key: JBTM-280 URL: http://jira.jboss.com/jira/browse/JBTM-280 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: Mark Little Looks like this is the best option now. -- 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, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-382) allow objectstore browser to run as applet from JBossAS console

by Jonathan Halliday (JIRA)

allow objectstore browser to run as applet from JBossAS console --------------------------------------------------------------- Key: JBTM-382 URL: http://jira.jboss.com/jira/browse/JBTM-382 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.3.0.GA Reporter: Jonathan Halliday Assigned To: Michael Musgrove Fix For: 4.4.CR2 The objectstore browser, or more generally the tooling framework it's based on, is a swing app. It would be nice if it also functioned as an applet, so we can integrate it with the management console for JBossAS 5. Maciej has already prototyped this, see https://svn.jboss.org/repos/labs/labs/jbosstm/workspace/jhalliday/mm_tool... Dust off this work, merge it back to trunk and figure out how best to package it. Additional considerations include the heuristics resolution work and remote operation (the applet running in a browser that's not on the same host as the AS instance it downloaded from). These may not make it into the AS 5.0 iteration. -- 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, 3 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2008