May 2010 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-742) AtomicAction and ThreadActionData cleanup is broken

by Andrew Dinn (JIRA)

AtomicAction and ThreadActionData cleanup is broken --------------------------------------------------- Key: JBTM-742 URL: https://jira.jboss.org/browse/JBTM-742 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6.1.CP05, 4.11.0 Reporter: Andrew Dinn Assignee: Mark Little Fix For: 4.12.0, 4.6.1.CP06 ThreadActionData emlpoys a ThreadLocal to maintain the association between threads and actions. This means that the association can only be removed by the associated thread. The finalize method on AtomicAction attempts, amongst other things, to ensure this association is broken by calling ThreadActionData.purgeAction(). Unfortunately it passes the current thread (the Finalizer thread) which means that the association is still retained. This also fails to remove any child thread from the basic action's child thread list for the same reason. Because it has no way of establishing the prior association this finalize method is an expensive waste of time. It would be best deleted. Also, another detail of this cleanup is wrong. AtomicAction.removeThread(t) currently calls ThreadActionData.purgeAction(this). It should call ThreadActionData.purgeAction(this, t). This change would allow a cleanup thread which knows about the association to remove the correct child thread from the basic action's child thread list. However, it will oto get round the problem that ThreadActionData is using a ThreadLocal. Again, since there is no way of knowing the prior association this method is probably redundant. -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-743) Invalid pom of jbossjts breaks AS build

by Carlo de Wolf (JIRA)

Invalid pom of jbossjts breaks AS build --------------------------------------- Key: JBTM-743 URL: https://jira.jboss.org/browse/JBTM-743 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Affects Versions: 4.11.0 Reporter: Carlo de Wolf Priority: Blocker Fix For: 4.12.0 [INFO] ------------------------------------------------------------------------ [INFO] Building JBoss Application Server IIOP [INFO] task-segment: [clean, install] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean] [INFO] [buildnumber:create {execution: set-build-properties}] [INFO] [build-helper:maven-version {execution: default}] Downloading: http://repository.jboss.org/maven2/org/jboss/jbossas/jboss-as-component-m... Downloading: http://repo1.maven.org/maven2/org/jboss/jbossas/jboss-as-component-matrix... [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: org.jboss.jbossas:jboss-as-component-matrix Reason: POM 'org.jboss.jbossas:jboss-as-component-matrix' not found in repository: Unable to download the artifact from any repository org.jboss.jbossas:jboss-as-component-matrix:pom:6.0.0.20100429-M3 from the specified remote repositories: snapshots.jboss.org (http://snapshots.jboss.org/maven2), central (http://repo1.maven.org/maven2), repository.jboss.org (http://repository.jboss.org/maven2) for project org.jboss.jbossas:jboss-as-component-matrix -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBTM-717) JDBC tests

by Mark Little (JIRA)

JDBC tests ---------- Key: JBTM-717 URL: https://jira.jboss.org/jira/browse/JBTM-717 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Resource Manager, Testing, Transaction Core Reporter: Mark Little Assignee: Jonathan Halliday Fix For: 4.11.0 We have a few JDBC classes in arjuna that aren't covered by unit tests. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-698) Improve test coverage for arjuna

by Mark Little (JIRA)

Improve test coverage for arjuna -------------------------------- Key: JBTM-698 URL: https://jira.jboss.org/jira/browse/JBTM-698 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Mark Little Assignee: Mark Little Fix For: 4.10.0 -- 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, 6 months

1
7
0 / 0

[JBoss JIRA] Created: (JBTM-739) update docs for 4.11

by Jonathan Halliday (JIRA)

update docs for 4.11 -------------------- Key: JBTM-739 URL: https://jira.jboss.org/jira/browse/JBTM-739 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-624) improve transaction reaper

by Jonathan Halliday (JIRA)

improve transaction reaper -------------------------- Key: JBTM-624 URL: https://jira.jboss.org/jira/browse/JBTM-624 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.8.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.9.0 As trunk now supports jdk6 minimum, we can take better advantage of java.util.concurrent to further streamline the reaper. Whilst we are at it, we should tidy things up a bit, use generics/autoboxing and other modern conveniences. -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-594) XARecoveryModule logging is incorrect

by Jonathan Halliday (JIRA)

XARecoveryModule logging is incorrect ------------------------------------- Key: JBTM-594 URL: https://jira.jboss.org/jira/browse/JBTM-594 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.8.0 com.arjuna.ats.internal.jta.recovery.info.rollingback is incorrectly used before the check which determines if the rollback will be done or not. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-740) update default test environment

by Jonathan Halliday (JIRA)

update default test environment ------------------------------- Key: JBTM-740 URL: https://jira.jboss.org/jira/browse/JBTM-740 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.6.1.CP04 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.6.1.CP05 Update test config to default to jdk 6 as 5 is now obsolete. -- 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, 7 months

1
1
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.12.0 (was: 4.11.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.12.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

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-696) NPE in TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:235)

by JÃ¶rg von Frantzius (JIRA)

NPE in TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:235) ------------------------------------------------------------------------- Key: JBTM-696 URL: https://jira.jboss.org/jira/browse/JBTM-696 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.2.3.SP7 Environment: Linux Reporter: JÃ¶rg von Frantzius In http://community.jboss.org/thread/142942?tstart=0 I've been told that JBOSS 4.2.3GA comes with JBossTS 4.2.3.SP7. We managed to see this exception with JBoss 4.2.3GA : Caused by: java.lang.NullPointerException at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:235) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86) at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140) at com.artnology.managedobject.impl.ManagedObjectManager.commitUnderlyingTx(ManagedObjectManager.java:5292) at com.artnology.managedobject.impl.ManagedObjectManager.commitTransaction(ManagedObjectManager.java:4838) What's a bit unusual about our transaction is that it does a lot of work during beforeCompletion, which might exceed the transaction timeout (but I don't know for sure that it did). Maybe a long user code activity during beforeCompletion can cause this confusion of _synchs possibly already having been nulled out. -- 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, 7 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2010