November 2011 - jbossts-issues - Jboss List Archives

[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

11 years, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (JBTM-850) Remove old ant build system in Narayana

by Tom Jenkinson (JIRA)

Remove old ant build system in Narayana --------------------------------------- Key: JBTM-850 URL: https://issues.jboss.org/browse/JBTM-850 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Fix For: 5.0.0.M1 To save the requirement of maintaining too build systems in Narayana we should remove the old Ant build system. This may also need removing for the qa/ module. *Potential* matches are: ./maven/build.xml ./ArjunaJTS/orbportability/build.xml ./ArjunaJTS/jtax/build.xml ./ArjunaJTS/trailmap/build.xml ./ArjunaJTS/build.xml ./ArjunaJTS/sharedbuild.xml ./ArjunaJTS/jts/build.xml ./ArjunaJTS/jacorb/idl/build.xml ./txbridge/demo/build.xml ./txbridge/build.xml ./txbridge/tests/build.xml ./ArjunaCore/txoj/build.xml ./ArjunaCore/build.xml ./ArjunaCore/arjuna/build.xml ./qa/build.xml ./qa/tests/build-jta.xml ./qa/tests/build-core.xml ./qa/tests/build-jts.xml ./qa/tests/product/build.xml ./build-release-pkgs.xml ./atsintegration/docbuild/build.xml ./atsintegration/build.xml ./common/build.xml ./antbuildsystem/build.xml ./ArjunaJTA/jdbc/build.xml ./ArjunaJTA/build.xml ./ArjunaJTA/jta/build.xml ./build.xml ./XTS/WSTX/build.xml ./XTS/bridge/build.xml ./XTS/sar/build.xml ./XTS/sar/tests/build.xml ./XTS/localjunit/build.xml ./XTS/WSCF/build.xml ./XTS/interop/WSTX11-interop/build.xml ./XTS/interop/WSTFSC07-interop/build.xml ./XTS/recovery/build.xml ./XTS/WS-T/build.xml ./XTS/demo/xts-build.xml ./XTS/demo/build.xml ./XTS/build.xml ./XTS/WSAS/build.xml ./XTS/WS-C/build.xml ./XTS/sharedbuild.xml ./rhq-plugin/build.xml ./docs/build.xml ./sharedbuild.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
9
0 / 0

[JBoss JIRA] Created: (JBTM-875) Convert the XTS demo project from ant to maven

by Paul Robinson (JIRA)

Convert the XTS demo project from ant to maven ---------------------------------------------- Key: JBTM-875 URL: https://issues.jboss.org/browse/JBTM-875 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Fix For: 5.0.0.M1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
15
0 / 0

[JBoss JIRA] Created: (JBTM-631) Generate proper maven artefacts

by Thomas Diesler (JIRA)

Generate proper maven artefacts ------------------------------- Key: JBTM-631 URL: https://jira.jboss.org/jira/browse/JBTM-631 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler The artefacts under jbossts (http://repository.jboss.org/maven2/jboss/jbossts/jbossjta) don't seem to be in sync with the project releases. * jbossjta-4.4.0.GA being the latest -- 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, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-659) support ipv6

by Jonathan Halliday (JIRA)

support ipv6 ------------ Key: JBTM-659 URL: https://jira.jboss.org/jira/browse/JBTM-659 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.10.0 The changes to Uid in JBTM-522 pave the way for full IPv6 support in the codebase. Although ad-hoc testing gives good results, we really need to modify the test setup and servers to ensure a reasonable subset of tests are run on IPv6. -- 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
22
0 / 0

[JBoss JIRA] (JBTM-940) Fix intermittant qa quite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2

by Tom Jenkinson (Created) (JIRA)

Fix intermittant qa quite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2 --------------------------------------------------------------------------------------------------- Key: JBTM-940 URL: https://issues.jboss.org/browse/JBTM-940 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Tom Jenkinson Fix For: 4.15.x, 5.0.0.M2 Assuming failure in test, rather than failed test: jbossts-trunk-java6 - Build # 925 - Still Failing! [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2 FAILED -- 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

5
18
0 / 0

[JBoss JIRA] Created: (JBTM-783) Test crash recovery when client, partiicpant and coordinator are deployed piecemeal

by Andrew Dinn (JIRA)

Test crash recovery when client, partiicpant and coordinator are deployed piecemeal ----------------------------------------------------------------------------------- Key: JBTM-783 URL: https://jira.jboss.org/browse/JBTM-783 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.12.0 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.13.0 -- 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

11 years, 7 months

4
10
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, 8 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, 8 months

5
14
0 / 0

[JBoss JIRA] Created: (JBTM-531) com.arjuna.ats.internal.jdbc.DynamicClass.shutdownDataSource(XADataSource) is never called

by Mauro Molinari (JIRA)

com.arjuna.ats.internal.jdbc.DynamicClass.shutdownDataSource(XADataSource) is never called ------------------------------------------------------------------------------------------ Key: JBTM-531 URL: https://jira.jboss.org/jira/browse/JBTM-531 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.6.0, 4.5.0 Reporter: Mauro Molinari Priority: Critical com.arjuna.ats.internal.jdbc.DynamicClass.shutdownDataSource(XADataSource) is never called by com.arjuna.ats.internal.jdbc.DirectRecoverableConnection. >From what I could understand (but I'm not sure of this), after calling com.arjuna.ats.internal.jdbc.DirectRecoverableConnection.closeCloseCurrentConnection() the DirectRecoverableConnection won't be used anymore, so that method could be a good candidate to call _dynamicConnection.shutDownDataSource(_theDataSource) and to null both _dynamicConnection and _theDataSource. This problem could be quite severe, because if the XADataSource needs to be shut down in order to release resources, this could lead to leaks. Moreover, I was wondering if a caching of the dynamic class wouldn't be a good idea... as of now, a NEW XA data source is created every time a new connection is requested... and this could be expensive... -- 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, 10 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2011