April 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2101) Blacktie integration CSTest hang

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2101: --------------------------------- The test setup is failed with starting the server with error "cannot start the same id server". It's caused by the .testsui queue not being deployed on the server. So it looks like the prev test tearDown does not wait for the server shutdow finishing. from the integration tests codes blacktie/integration-tests/src/test/java/org/jboss/narayana/blacktie/jatmibroker/xatmi/CSControl.java {code} public void tearDown() { log.info("tearDown"); try { if (server != null) { log.debug("destroying server process"); server.interrupt(); server.getProcess().destroy(); log.debug("destroyed server process"); server.getProcess().waitFor(); } log.debug("waited for server process"); } catch (Throwable e) { throw new RuntimeException("Server shutdown error: ", e); } } {code} It looks like it does not need to destroy the process and just wait for it exits. > Blacktie integration CSTest hang > -------------------------------- > > Key: JBTM-2101 > URL: https://issues.jboss.org/browse/JBTM-2101 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACK... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2357) jbossts-properties.xml not loaded if arjuna-properties-file not set in manifest

by Toby Crawley (JIRA)

Toby Crawley created JBTM-2357: ---------------------------------- Summary: jbossts-properties.xml not loaded if arjuna-properties-file not set in manifest Key: JBTM-2357 URL: https://issues.jboss.org/browse/JBTM-2357 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.0.3 Reporter: Toby Crawley Assignee: Tom Jenkinson If the property isn't set, ConfigurationInfo falls back to looking for "arjuna-properties.xml" because of https://github.com/jbosstm/narayana/blob/master/common/classes/com/arjuna.... Is that default intentional, or should it have been set to "jbossts-properties.xml" as part of JBTM-482? We're running in to this with [Immutant|http://immutant.org], where the user can run their application as a set of jars or as an uberjar. When ran as a set of jars, the manifest from narayana-jta.jar has arjuna-properties-file set, and the jar provides a jbossts-properties.xml at the top level that gets loaded. But when the user creates an uberjar (a process we don't control), the uberjar includes the jbossts-properties.xml file from the jta jar, but does not include the arjuna-properties-file property in the manifest, which causes narayana to fail because the node id isn't set. We'd prefer the same behavior in either run mode, so currently provide an arjuna-properties.xml that is identical to the default from the jta jar to work around the issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2259) Allow the ordering of some synchronizations to be configurable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2259?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2259: ----------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Rejected See comment https://developer.jboss.org/message/923571#923571 > Allow the ordering of some synchronizations to be configurable > --------------------------------------------------------------- > > Key: JBTM-2259 > URL: https://issues.jboss.org/browse/JBTM-2259 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 6.x.y > > > IronJacamar delists resources in a beforeCompletion synchronization but under certain circumstances (see attached forum thread) it may run before all JPA persistence providers beforeCompletion synchronizations have been called (which breaks JPA). > The request is to add a configuration option to control the order in which certain synchronizations are called. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2349) CompensationContext is destroyed once the first handler is invoked

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2349?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2349: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CompensationContext is destroyed once the first handler is invoked > ------------------------------------------------------------------ > > Key: JBTM-2349 > URL: https://issues.jboss.org/browse/JBTM-2349 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.5 > > > https://github.com/jbosstm/narayana/blob/master/compensations/src/main/ja... > https://github.com/jbosstm/narayana/blob/master/compensations/src/main/ja... > If there are two handlers (compensation or confirmation), which need to access the same compensation scoped object, only the first one will succeed. Once the first handler is invoked from the ParticipantImpl, CompensationScope is destroyed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2353) Compensation handler interceptors should not throw exception, if there is no transaction

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2353?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2353: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Compensation handler interceptors should not throw exception, if there is no transaction > ---------------------------------------------------------------------------------------- > > Key: JBTM-2353 > URL: https://issues.jboss.org/browse/JBTM-2353 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > @TXCompensate, @TXConfirm, and @TxLogged interceptors throw exception, if there is not transaction. However, transaction availability check is also done by @Compensatable interceptor. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2139) update the narayana-quickstart jobs to make sure the txfooapp example is working

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2139?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2139: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > update the narayana-quickstart jobs to make sure the txfooapp example is working > -------------------------------------------------------------------------------- > > Key: JBTM-2139 > URL: https://issues.jboss.org/browse/JBTM-2139 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1572) a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1572?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1572: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/124 > a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't > ------------------------------------------------------------------------------------------------ > > Key: JBTM-1572 > URL: https://issues.jboss.org/browse/JBTM-1572 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.5 > > Attachments: client.valgrind, JBTM-1572.txt, JBTM-1572.zip, server.valgrind, windbg.out > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Note, it will definitely be worth doing this in a branch/pull as I suspect the database isn't running atm so that will need a kick too -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1572) a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1572?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1572: -------------------------------- Fix Version/s: 5.0.5 (was: 5.x.y) > a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't > ------------------------------------------------------------------------------------------------ > > Key: JBTM-1572 > URL: https://issues.jboss.org/browse/JBTM-1572 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.5 > > Attachments: client.valgrind, JBTM-1572.txt, JBTM-1572.zip, server.valgrind, windbg.out > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Note, it will definitely be worth doing this in a branch/pull as I suspect the database isn't running atm so that will need a kick too -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2139) update the narayana-quickstart jobs to make sure the txfooapp example is working

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2139?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2139: -------------------------------- Fix Version/s: 5.0.5 (was: 5.x.y) > update the narayana-quickstart jobs to make sure the txfooapp example is working > -------------------------------------------------------------------------------- > > Key: JBTM-2139 > URL: https://issues.jboss.org/browse/JBTM-2139 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2356) REST-AT recovery failure

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2356?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2356: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/821 > REST-AT recovery failure > ------------------------ > > Key: JBTM-2356 > URL: https://issues.jboss.org/browse/JBTM-2356 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > See linked forum post: > Start two serves A and B with the coordinator running on A and a participant on server B. Crash server B just before commit. When server B comes back up the coordinator fails to recover the transaction and returns 404 when asked about the transaction. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2015