July 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-893) Build is dependent upon Sun's JDK

by Tom Jenkinson (JIRA)

Build is dependent upon Sun's JDK --------------------------------- Key: JBTM-893 URL: https://issues.jboss.org/browse/JBTM-893 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.0.0.M2 We have a dependency in the arjuna module on jconsole.jar which is not shipped in openjdk for instance so our pom refers to JAVA_HOME/lib/jconsole.jar. This needs reviewing, we could add a profile that only includes the dependency on a build when the file exists and in other profiles does not build the classes that require this Jar, but if the code is critical we need to think about a rewrite to not depend on the (presumably) proprietary Jar. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JBTM-486) Refactor log store

by Mark Little (JIRA)

Refactor log store ------------------ Key: JBTM-486 URL: https://jira.jboss.org/jira/browse/JBTM-486 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.6 Reporter: Mark Little Assignee: Mark Little Priority: Minor Fix For: 4.7 The new log store could do with some refactoring. No interface changes or modifications of data structures. -- 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

12 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBTM-844) Remove support for 1.0 XTS api

by Tom Jenkinson (JIRA)

Remove support for 1.0 XTS api ------------------------------ Key: JBTM-844 URL: https://issues.jboss.org/browse/JBTM-844 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson The community supported feature appears to be no longer required. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBTM-877) Commit the Emma patch to svn

by Paul Robinson (JIRA)

Commit the Emma patch to svn ---------------------------- Key: JBTM-877 URL: https://issues.jboss.org/browse/JBTM-877 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M1 Andrew Dinn currently has the patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] (JBTM-1088) Port trailmap project from ant to maven

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1088: ----------------------------------- Summary: Port trailmap project from ant to maven Key: JBTM-1088 URL: https://issues.jboss.org/browse/JBTM-1088 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M2 -- 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

12 years, 1 month

1
7
0 / 0

[JBoss JIRA] Created: (JBTM-673) Investigate other object store implementations

by Mark Little (JIRA)

Investigate other object store implementations ---------------------------------------------- Key: JBTM-673 URL: https://jira.jboss.org/jira/browse/JBTM-673 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 "... spin out messaging journal into separate component so we can consume it. Also look at other disk I/O alternatives, basically trying to batch syncs so one is shared by many tx rather than one per tx. Also maybe preliminary investigation of in-memory replication of logs via jgroups." See related links. Need to re-check performance of transaction log and maybe make it the default implementation. -- 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

12 years, 1 month

2
12
0 / 0

[JBoss JIRA] Created: (JBTM-634) Make sources and javadoc available

by Thomas Diesler (JIRA)

Make sources and javadoc available ---------------------------------- Key: JBTM-634 URL: https://jira.jboss.org/jira/browse/JBTM-634 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler IDEs like Eclipse and IntelliJ allow you to download sources and javadoc automatically from the maven repo Please make these available for the jbossjta releases -- 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

12 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JBTM-633) Generate meaningful POM

by Thomas Diesler (JIRA)

Generate meaningful POM ----------------------- Key: JBTM-633 URL: https://jira.jboss.org/jira/browse/JBTM-633 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler The POM should contain meaningful information, like dependencies, SVN location, etc Currently this probably generated by deploy:deploy-file <project> <modelVersion>4.0.0</modelVersion> <groupId>jboss.jbossts</groupId> <artifactId>jbossjta</artifactId> <version>4.4.0.GA</version> </project> -- 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

12 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBTM-873) "Unique index or primary key violation" in jee_transactional_app quickstart

by Paul Robinson (JIRA)

"Unique index or primary key violation" in jee_transactional_app quickstart --------------------------------------------------------------------------- Key: JBTM-873 URL: https://issues.jboss.org/browse/JBTM-873 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Reporter: Paul Robinson Assignee: Tom Jenkinson Fix For: 5.0.0.M1 Attachments: log.txt To reproduce: {code} cd ArjunaJTA/quickstarts/jee_transactional_app export JBOSS_HOME=<PATH_TO_JBOSS_HOME> mvn install -Parq-jbossas-managed {code} Observe stack traces in logs. Notice that this error doesn't cause the tests to fail. See attached logs for what I am seeing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
10
0 / 0

[JBoss JIRA] (JBTM-1209) XTS recovery tests failing due to a non-empty TXObjectStore after test complete

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1209: ----------------------------------- Summary: XTS recovery tests failing due to a non-empty TXObjectStore after test complete Key: JBTM-1209 URL: https://issues.jboss.org/browse/JBTM-1209 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-java7/411/console Looking at http://172.17.131.2/job/narayana-java7/411/artifact/XTS/localjunit/crash-... you will see: {code} java.lang.AssertionError at org.junit.Assert.fail(Assert.java:92) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertTrue(Assert.java:54) at com.arjuna.qa.junit.BaseCrashTest.tearDown(BaseCrashTest.java:105) {code} This assertion checks that the TXObjectStore is empty after the test completes. For the three tests that failed in this job, the log was not empty. Looking at the end of http://172.17.131.2/job/narayana-java7/411/artifact/XTS/localjunit/crash-... shows you: {code} [0m[0m10:36:04,605 INFO [stdout] (Periodic Recovery) rule.debug{trace remove committed state} : removed committed transaction 0:ffffac118303:4e49dd0f:50110ed5:10 [0m[0m10:36:04,605 INFO [stdout] (Periodic Recovery) rule.debug{trace remove committed state} : !!!killing JVM!!! {code} This suggests that the transaction log was removed. However, I'm not sure that the Byteman script checks that the participant record has also been removed. It's possible that the AS is being killed slightly too early, before the participant record is removed. We should check other scripts to see if they wait for both logs to be removed. [JBTM-1208] should help debug this problem if we get it again. -- 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

12 years, 1 month

3
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2012