March 2010 - jbossts-issues - Jboss List Archives

[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

13 years, 11 months

2
4
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

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-489) WS-T 1.1. implementation is generating invalid faults

by Andrew Dinn (JIRA)

WS-T 1.1. implementation is generating invalid faults ----------------------------------------------------- Key: JBTM-489 URL: https://jira.jboss.org/jira/browse/JBTM-489 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.5 Reporter: Andrew Dinn Assignee: Andrew Dinn The WS-C 1.1. spec employs a slightly different set of SOAP fault codes to the 1.0 implementation. The current 1.1. implementation is still generating faults included in the 1.0 set but not in the 1.1 set, for example, NO_ACTIVITY. This may lead to interopability issues. All fault cases should be checked and, where necessary, corrected to generate faults which conform to the specification. -- 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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-625) Incorrect serialization of XTS 1.1 context into service rrequests breaks interop

by Andrew Dinn (JIRA)

Incorrect serialization of XTS 1.1 context into service rrequests breaks interop -------------------------------------------------------------------------------- Key: JBTM-625 URL: https://jira.jboss.org/jira/browse/JBTM-625 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.8.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.9.0 The XTS 1.1. client and service SOAP handlers which serialize and deserialize the transaction context into/out of web service requests are not generating the headers correctly. During serialization the context is embedded into a wscoor:CoordinationContext header element, i.e. the message contains two nested elements with this tag. The mistake is consistent in the deserialization code so it does not show during normal.JBoss to JBoss operation. However., it does break interoperability. -- 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

13 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBTM-718) Improve reaper test coverage

by Mark Little (JIRA)

Improve reaper test coverage ---------------------------- Key: JBTM-718 URL: https://jira.jboss.org/jira/browse/JBTM-718 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing, Transaction Core Reporter: Mark Little Assignee: Andrew Dinn Fix For: 4.11.0 Pretty basic these days given the complexity and richness of the new reaper code. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-727) Emma coverage missing some method invocations

by Mark Little (JIRA)

Emma coverage missing some method invocations --------------------------------------------- Key: JBTM-727 URL: https://jira.jboss.org/jira/browse/JBTM-727 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Mark Little Assignee: Andrew Dinn Fix For: 4.11.0 There are some class that emma says don't have coverage and yet there are tests that do cover them (and I have confirmed the methods get called). For instance ServerTopLevelOSIActionUnitTest which covers ServerOSITopLevelAction. The commit and rollback methods are invoked, yet emma misses them. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-706) XTS test code should upgrade to use same junit as TS build then ensure it links it from the TS tree

by Andrew Dinn (JIRA)

XTS test code should upgrade to use same junit as TS build then ensure it links it from the TS tree --------------------------------------------------------------------------------------------------- Key: JBTM-706 URL: https://jira.jboss.org/jira/browse/JBTM-706 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.9.0 Reporter: Andrew Dinn Assignee: Andrew Dinn -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBTM-711) Make 'ant clean' clean up all artifacts

by Mark Little (JIRA)

Make 'ant clean' clean up all artifacts --------------------------------------- Key: JBTM-711 URL: https://jira.jboss.org/jira/browse/JBTM-711 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Mark Little Assignee: Jonathan Halliday Fix For: 4.11.0 Currently a lot of extraneous artifacts remain. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-733) streamline debug level logging

by Jonathan Halliday (JIRA)

streamline debug level logging ------------------------------ Key: JBTM-733 URL: https://jira.jboss.org/jira/browse/JBTM-733 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common, Configuration Affects Versions: 4.10.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 The debug level logging in JBossTS is unnecessarily complex. DebugLevel values other than 0xffffffff ('ON') and 0x00000000 ('OFF'), FacilityCode and VisibilityLevel filters are largely unused. In practice the use case for debug level logging is for customers to pass trace information back to support. In such cases we inevitably want everything and will filter it later with grep according to the case at hand. The additional verbosity that DebugLevel, FacilityCode and VisibilityLevel add to the codebase is unwarranted. These classes should be nuked. Removing this added complexity will also help make the transition to the new common JBoss logging system (TAG-3) easier. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-724) ensure consistent recovery module passes

by Jonathan Halliday (JIRA)

ensure consistent recovery module passes ---------------------------------------- Key: JBTM-724 URL: https://jira.jboss.org/jira/browse/JBTM-724 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.10.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.11.0 PeriodicRecovery should ensure that the same set of modules is used for the first and second pass, as some implementations will not work if only one or the other pass is run. -- 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

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2010