September 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1194) TXFramework tests fail intermittently on Java7

by Paul Robinson (JIRA)

11 years, 7 months

2
3
0 / 0

[JBoss JIRA] (JBTM-1243) TXFramework running with jboss-as-7.2.0.Alpha1 fail with ava.lang.NoClassDefFoundError: org/jboss/as/osgi/deployment/OSGiDeploymentAttachment

by Amos Feng (JIRA)

Amos Feng created JBTM-1243: ------------------------------- Summary: TXFramework running with jboss-as-7.2.0.Alpha1 fail with ava.lang.NoClassDefFoundError: org/jboss/as/osgi/deployment/OSGiDeploymentAttachment Key: JBTM-1243 URL: https://issues.jboss.org/browse/JBTM-1243 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Demonstrator, TXFramework Affects Versions: 5.0.0.M1 Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.0.M2 Paul and I both think it's probably due to a missmatched arquillian dep -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
4
0 / 0

[JBoss JIRA] (JBTM-1031) Search for "<String.class> == <String.class>" bugs

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1031: ----------------------------------- Summary: Search for "<String.class> == <String.class>" bugs Key: JBTM-1031 URL: https://issues.jboss.org/browse/JBTM-1031 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Reporter: Paul Robinson Assignee: Amos Feng Priority: Minor Fix For: 5.0.0.M2 A recent bug in XTS recovery was caused by the use of == to compare Strings. String#equals(...) should have been used. We need to search the XTS codebase for other occurrences of this type of bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
5
0 / 0

[JBoss JIRA] (JBTM-1181) Add JBOSS Transactional File I/O User Guide TXFileInJava into documentation repo and use jdocbook

by Amos Feng (JIRA)

Amos Feng created JBTM-1181: ------------------------------- Summary: Add JBOSS Transactional File I/O User Guide TXFileInJava into documentation repo and use jdocbook Key: JBTM-1181 URL: https://issues.jboss.org/browse/JBTM-1181 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.0.Final there is https://svn.jboss.org/repos/labs/labs/jbosstm/workspace/transactionalFile... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
4
0 / 0

[JBoss JIRA] (JBTM-1137) ArjunaJTS recovery quickstart sometimes throws CORBA.OBJECT_NOT_EXIST exception

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1137: -------------------------------------- Summary: ArjunaJTS recovery quickstart sometimes throws CORBA.OBJECT_NOT_EXIST exception Key: JBTM-1137 URL: https://issues.jboss.org/browse/JBTM-1137 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 5.0.0.M1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 6.0.0.Final Running the JTS recovery quickstart (ArjunaJTS/recovery) sometimes, but not always, throws an org.omg.CORBA.OBJECT_NOT_EXIST exception during recovery. When it does happen the relevant XA resoruces still complete but the corresponding log record is left in the ObjectStore and then moved to AssumedComplete on the next pass. When it does happen I notice that there are two threads replaying phase 2, the one that completes removes the servants (for the XA resources) from the ORBs active object map so that when the other thread replays phase 2 the CORBA object no longer exists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] (JBTM-1183) XA connections leak in XARecoveryModule

by v a (JIRA)

v a created JBTM-1183: ------------------------- Summary: XA connections leak in XARecoveryModule Key: JBTM-1183 URL: https://issues.jboss.org/browse/JBTM-1183 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 4.16.4 Environment: JBoss AS 7.1.x, 7.2.0.Alpha1 Reporter: v a Assignee: Tom Jenkinson Priority: Critical XARecoveryModule._xidScans accumulates XA connections if JDBC driver does not implement Connection.isValid(int timeout) method. It's the case for PostgreSQL JDBC driver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

6
12
0 / 0

[JBoss JIRA] Created: (JBTM-576) update unit tests

by Jonathan Halliday (JIRA)

update unit tests ----------------- Key: JBTM-576 URL: https://jira.jboss.org/jira/browse/JBTM-576 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.7.0 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.8.0 There are many unit tests that have lain dormant for some time. Convert them from DTF/junit3 to junit4, wire them to the build and make them pass. This will be done incrementally, one module at a time, following the dependency chain e.g. common, ArjunaCore/arjuna, ArjunaCore/txoj, ... JTA/, .../JTS/... -- 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

11 years, 7 months

4
14
0 / 0

[JBoss JIRA] Created: (JBTM-522) Update UID to support ipv6 and ipv4

by Mark Little (JIRA)

Update UID to support ipv6 and ipv4 ----------------------------------- Key: JBTM-522 URL: https://jira.jboss.org/jira/browse/JBTM-522 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.6.0 Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.0 It's possible to have a version that supports both v4 and v6. -- 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

11 years, 7 months

5
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2012