November 2009 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-646) AT subordinate implementation leaves window where prepared subordinate TX may be orphaned and not rolled back

by Andrew Dinn (JIRA)

AT subordinate implementation leaves window where prepared subordinate TX may be orphaned and not rolled back ------------------------------------------------------------------------------------------------------------- Key: JBTM-646 URL: https://jira.jboss.org/jira/browse/JBTM-646 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6.1.CP03, 4.8.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.9.0, 4.6.1.CP04 The AT subordinate implementation employs a proxy participant registered on behalf of the suibordinate transaction to forward messages from the parent coordinator. There is a window during prepare between completion of the subordinate transaction prepare (which includes logging the subordinate transaction) and logging of the proxy where a crash can occur. When the subordinate transaction is recovered it will wait forever for a message from a non-existent proxy. This can be resolved by ensuring that recovered subordinates and their proxies are reconciled during the first pass of the log. Any transactions whose proxy is not present can be rolled back automatically. This mirrors the way the BA subordinate transaction implementation closes the window. -- 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBTM-44) Transaction bridging

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-44?page=com.atlassian.jira.plugin... ] Jonathan Halliday updated JBTM-44: ---------------------------------- Fix Version/s: 4.10.0 (was: 4.9.0) > Transaction bridging > -------------------- > > Key: JBTM-44 > URL: https://jira.jboss.org/jira/browse/JBTM-44 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTA, JTS, XTS > Reporter: Mark Little > Assignee: Jonathan Halliday > Priority: Critical > Fix For: 4.10.0 > > Attachments: jbossxts-bridge.zip > > -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-390) add ability to run DTF tests locally without DTF server

by Jonathan Halliday (JIRA)

add ability to run DTF tests locally without DTF server ------------------------------------------------------- Key: JBTM-390 URL: https://jira.jboss.org/jira/browse/JBTM-390 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Release Process, Testing Affects Versions: 4.4.CR1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.4.CR2 JBossTS has a substantial investment in DTF tests. However, running these is a complex process, involving building and deploying to a pre-configured DTF instance or installing the DTF locally on the developer's workstation, including tomcat, mysql etc. Now the DTF is open source and the tests are likewise in the public repository, it would be nice for developers to be able to run them with less hassle, much like unit tests. This issue is tightly integrated with DTF-4, which covers provision of the necessary functionality in DTF. -- 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

15 years, 2 months

1
13
0 / 0

[JBoss JIRA] Created: (JBTM-399) Set up continuous integration build system

by Mark Little (JIRA)

Set up continuous integration build system ------------------------------------------ Key: JBTM-399 URL: https://jira.jboss.org/jira/browse/JBTM-399 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Mark Little Maybe running mini-QA setup from old Arjuna days? -- 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

15 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-628) provide bean based configuration, part 2

by Jonathan Halliday (JIRA)

provide bean based configuration, part 2 ---------------------------------------- Key: JBTM-628 URL: https://jira.jboss.org/jira/browse/JBTM-628 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 Further cleanup and refinement for the configuration system, following on from the changes introduced in JBTM-596 -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-627) refactor AbstractRecord sort order handling

by Jonathan Halliday (JIRA)

refactor AbstractRecord sort order handling ------------------------------------------- Key: JBTM-627 URL: https://jira.jboss.org/jira/browse/JBTM-627 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Transaction Core Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 AbstractRecords can be ordering using one of two different algorithms. The configuration setting is read on each comparison, which is expensive. It should be read at startup and cached. The config should come via the new beans mechanism, not a build time setting. -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-653) refactor Xid handling

by Jonathan Halliday (JIRA)

refactor Xid handling --------------------- Key: JBTM-653 URL: https://jira.jboss.org/jira/browse/JBTM-653 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA, JTS, Transaction Core Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 Xid handling is a horrible mess. Creation is excruciatingly slow because XATxConverter uses Uid.stringFrom, then promptly turns the string back into a bunch of bytes. XID has no business being in ArjunaCore, or indeed externally exposed at all - it should be internal to XidImple. Some static utility methods on XATxConverter and elsewhere would be better off in XidImple too. -- 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-595) Add support for JBoss LogManager backend

by David Lloyd (JIRA)

Add support for JBoss LogManager backend ---------------------------------------- Key: JBTM-595 URL: https://jira.jboss.org/jira/browse/JBTM-595 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Common Reporter: David Lloyd Priority: Minor The new log manager in AS 6.0 supports internationalization and localization natively. Provide an implementation which does not rely on log4j or JCL anymore since those technologies are bug-ridden and obsolete. Patch attached. -- 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

15 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-655) clean up atsintegration

by Jonathan Halliday (JIRA)

clean up atsintegration ----------------------- Key: JBTM-655 URL: https://jira.jboss.org/jira/browse/JBTM-655 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 atsintegration needs a bit of housekeeping, particularly with regard to dependencies. For example, publishing of components to JMX is now done by MC annotations and exposing the JMX to remote clients is the AS's problem, not an issue for JBossTS. Hence, throw out the JMX agent stuff. Move from jboss logging to JBossTS logging to drop that dep also (and as a bonus facilitate i18n, see JBTM-414). -- 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

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-555) make memory leak tests more robust

by Jonathan Halliday (JIRA)

make memory leak tests more robust ---------------------------------- Key: JBTM-555 URL: https://jira.jboss.org/jira/browse/JBTM-555 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing, Transaction Core Affects Versions: 4.6.1 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: future Some tests in the txcore group attempt to detect memory leaks by setup System.gc() take memory reading doTransactionStuff System.gc() take another memory reading This is unreliable, as System.gc() is only advisory to the runtime. There is no way to FORCE gc from within the jvm. This causes the tests to be somewhat unreliable. Dirty tricks to work around this include running the tests with a small heap (-Xmx5m). With less free space to work with, the gc tries harder. On a default size heap it mostly ignores System.gc(). Unfortunately the test framework does not make it easy to set -Xmx on a per test / test group basis. Similar effect could perhaps be achieved by allocating all except a small portion of the available heap from within the vm using eg. new byte[]. There is also the jvmti ForceGarbageCollection method, but that would require us to have a chunk of C code on each test platform, which is a pain. -- 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

15 years, 2 months

2
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2009