October 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2780) JTS recovery does not process commit when connection is halt during 2PC

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2780?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2780: ---------------------------------- Steps to Reproduce: The behavior could be observed when jts test is run in crashrec testsuite. Test does not fail every time as it could happen that txn is rolled back and MDB then process the message for second time and thus the final checks can observe message being committed. But the server log always show what was the process. {code} git clone http://git.app.eng.bos.redhat.com/git/jbossqe-eap-tests-transactions.git export JBOSS_HOME=... (downloadable at http://download.eng.brq.redhat.com/devel/candidates/JBEAP/) mvn clean verify -am -pl jbossts -DfailIfNoTests=false -Djbossts.noJTA -Dtest=JMSProxyMdbMessagingServerCrashRecoveryTestCase#haltConnectionAfterDbCommits {code} was: The behavior could be observed when jts test is run in crashrec testsuite {code} git clone http://git.app.eng.bos.redhat.com/git/jbossqe-eap-tests-transactions.git export JBOSS_HOME=... (downloadable at http://download.eng.brq.redhat.com/devel/candidates/JBEAP/) mvn clean verify -am -pl jbossts -DfailIfNoTests=false -Djbossts.noJTA -Dtest=JMSProxyMdbMessagingServerCrashRecoveryTestCase#haltConnectionAfterDbCommits {code} > JTS recovery does not process commit when connection is halt during 2PC > ----------------------------------------------------------------------- > > Key: JBTM-2780 > URL: https://issues.jboss.org/browse/JBTM-2780 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Recovery > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Critical > Attachments: .jts_haltConnectionAfterDbCommits_server.log.syntax, haltConnectionAfterDbCommits_standalone-full.xml > > > I experience wrong behavior of JTS implementation in following test scenario. This seems to be a regression against behavior of recovery for 7.0.0.GA. > # there is two jboss eap 7.1.0.DR6 servers used. First deploys MDB and does periodic recovery. Second is used only as a Artemis messaging broker. > # first app server receives a message via MDB #onMessage from artemis broker (second eap server) > # during onMessage processing a enw message is send to different remote queue on artemis broker > # testing XA resource is enlisted to txn > # prepare phase passes for all 3 resources - mdb inbound, outbound queue, test xa resource > # connection to the second server is halt at time when commit message of MDB resource is sent to artemis broker but the confirmation is not delivered back to TM > # commit of MDB as xa resource and outbound queue as resource fail - XAException.XA_RETRY is returned > # the test XAResource is committed > # recovery starts work and log shows that XAResourceRecord.commit is called at some point of time but the real commit on the XAResource is not done and transaction is rolled back at the end > The expected behavior (and what I can observe for JTA as well) is that recovery process should commit the outbound connection resource (MDB resource should be committed just not confirmed back from artemis broker to TM). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2780) JTS recovery does not process commit when connection is halt during 2PC

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-2780: ------------------------------------- Summary: JTS recovery does not process commit when connection is halt during 2PC Key: JBTM-2780 URL: https://issues.jboss.org/browse/JBTM-2780 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Ondra Chaloupka Priority: Critical Attachments: .jts_haltConnectionAfterDbCommits_server.log.syntax, haltConnectionAfterDbCommits_standalone-full.xml I experience wrong behavior of JTS implementation in following test scenario. This seems to be a regression against behavior of recovery for 7.0.0.GA. # there is two jboss eap 7.1.0.DR6 servers used. First deploys MDB and does periodic recovery. Second is used only as a Artemis messaging broker. # first app server receives a message via MDB #onMessage from artemis broker (second eap server) # during onMessage processing a enw message is send to different remote queue on artemis broker # testing XA resource is enlisted to txn # prepare phase passes for all 3 resources - mdb inbound, outbound queue, test xa resource # connection to the second server is halt at time when commit message of MDB resource is sent to artemis broker but the confirmation is not delivered back to TM # commit of MDB as xa resource and outbound queue as resource fail - XAException.XA_RETRY is returned # the test XAResource is committed # recovery starts work and log shows that XAResourceRecord.commit is called at some point of time but the real commit on the XAResource is not done and transaction is rolled back at the end The expected behavior (and what I can observe for JTA as well) is that recovery process should commit the outbound connection resource (MDB resource should be committed just not confirmed back from artemis broker to TM). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2780) JTS recovery does not process commit when connection is halt during 2PC

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2780?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2780: ---------------------------------- Attachment: .jts_haltConnectionAfterDbCommits_server.log.syntax haltConnectionAfterDbCommits_standalone-full.xml > JTS recovery does not process commit when connection is halt during 2PC > ----------------------------------------------------------------------- > > Key: JBTM-2780 > URL: https://issues.jboss.org/browse/JBTM-2780 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Priority: Critical > Attachments: .jts_haltConnectionAfterDbCommits_server.log.syntax, haltConnectionAfterDbCommits_standalone-full.xml > > > I experience wrong behavior of JTS implementation in following test scenario. This seems to be a regression against behavior of recovery for 7.0.0.GA. > # there is two jboss eap 7.1.0.DR6 servers used. First deploys MDB and does periodic recovery. Second is used only as a Artemis messaging broker. > # first app server receives a message via MDB #onMessage from artemis broker (second eap server) > # during onMessage processing a enw message is send to different remote queue on artemis broker > # testing XA resource is enlisted to txn > # prepare phase passes for all 3 resources - mdb inbound, outbound queue, test xa resource > # connection to the second server is halt at time when commit message of MDB resource is sent to artemis broker but the confirmation is not delivered back to TM > # commit of MDB as xa resource and outbound queue as resource fail - XAException.XA_RETRY is returned > # the test XAResource is committed > # recovery starts work and log shows that XAResourceRecord.commit is called at some point of time but the real commit on the XAResource is not done and transaction is rolled back at the end > The expected behavior (and what I can observe for JTA as well) is that recovery process should commit the outbound connection resource (MDB resource should be committed just not confirmed back from artemis broker to TM). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2780) JTS recovery does not process commit when connection is halt during 2PC

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2780?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2780: ---------------------------------- Affects Version/s: 5.3.5.Final > JTS recovery does not process commit when connection is halt during 2PC > ----------------------------------------------------------------------- > > Key: JBTM-2780 > URL: https://issues.jboss.org/browse/JBTM-2780 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Critical > Attachments: .jts_haltConnectionAfterDbCommits_server.log.syntax, haltConnectionAfterDbCommits_standalone-full.xml > > > I experience wrong behavior of JTS implementation in following test scenario. This seems to be a regression against behavior of recovery for 7.0.0.GA. > # there is two jboss eap 7.1.0.DR6 servers used. First deploys MDB and does periodic recovery. Second is used only as a Artemis messaging broker. > # first app server receives a message via MDB #onMessage from artemis broker (second eap server) > # during onMessage processing a enw message is send to different remote queue on artemis broker > # testing XA resource is enlisted to txn > # prepare phase passes for all 3 resources - mdb inbound, outbound queue, test xa resource > # connection to the second server is halt at time when commit message of MDB resource is sent to artemis broker but the confirmation is not delivered back to TM > # commit of MDB as xa resource and outbound queue as resource fail - XAException.XA_RETRY is returned > # the test XAResource is committed > # recovery starts work and log shows that XAResourceRecord.commit is called at some point of time but the real commit on the XAResource is not done and transaction is rolled back at the end > The expected behavior (and what I can observe for JTA as well) is that recovery process should commit the outbound connection resource (MDB resource should be committed just not confirmed back from artemis broker to TM). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2780) JTS recovery does not process commit when connection is halt during 2PC

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2780?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2780: ---------------------------------- Component/s: JTS Recovery > JTS recovery does not process commit when connection is halt during 2PC > ----------------------------------------------------------------------- > > Key: JBTM-2780 > URL: https://issues.jboss.org/browse/JBTM-2780 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Recovery > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Critical > Attachments: .jts_haltConnectionAfterDbCommits_server.log.syntax, haltConnectionAfterDbCommits_standalone-full.xml > > > I experience wrong behavior of JTS implementation in following test scenario. This seems to be a regression against behavior of recovery for 7.0.0.GA. > # there is two jboss eap 7.1.0.DR6 servers used. First deploys MDB and does periodic recovery. Second is used only as a Artemis messaging broker. > # first app server receives a message via MDB #onMessage from artemis broker (second eap server) > # during onMessage processing a enw message is send to different remote queue on artemis broker > # testing XA resource is enlisted to txn > # prepare phase passes for all 3 resources - mdb inbound, outbound queue, test xa resource > # connection to the second server is halt at time when commit message of MDB resource is sent to artemis broker but the confirmation is not delivered back to TM > # commit of MDB as xa resource and outbound queue as resource fail - XAException.XA_RETRY is returned > # the test XAResource is committed > # recovery starts work and log shows that XAResourceRecord.commit is called at some point of time but the real commit on the XAResource is not done and transaction is rolled back at the end > The expected behavior (and what I can observe for JTA as well) is that recovery process should commit the outbound connection resource (MDB resource should be committed just not confirmed back from artemis broker to TM). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2780) JTS recovery does not process commit when connection is halt during 2PC

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2780?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned JBTM-2780: ------------------------------------- Assignee: Tom Jenkinson > JTS recovery does not process commit when connection is halt during 2PC > ----------------------------------------------------------------------- > > Key: JBTM-2780 > URL: https://issues.jboss.org/browse/JBTM-2780 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Critical > Attachments: .jts_haltConnectionAfterDbCommits_server.log.syntax, haltConnectionAfterDbCommits_standalone-full.xml > > > I experience wrong behavior of JTS implementation in following test scenario. This seems to be a regression against behavior of recovery for 7.0.0.GA. > # there is two jboss eap 7.1.0.DR6 servers used. First deploys MDB and does periodic recovery. Second is used only as a Artemis messaging broker. > # first app server receives a message via MDB #onMessage from artemis broker (second eap server) > # during onMessage processing a enw message is send to different remote queue on artemis broker > # testing XA resource is enlisted to txn > # prepare phase passes for all 3 resources - mdb inbound, outbound queue, test xa resource > # connection to the second server is halt at time when commit message of MDB resource is sent to artemis broker but the confirmation is not delivered back to TM > # commit of MDB as xa resource and outbound queue as resource fail - XAException.XA_RETRY is returned > # the test XAResource is committed > # recovery starts work and log shows that XAResourceRecord.commit is called at some point of time but the real commit on the XAResource is not done and transaction is rolled back at the end > The expected behavior (and what I can observe for JTA as well) is that recovery process should commit the outbound connection resource (MDB resource should be committed just not confirmed back from artemis broker to TM). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2779) Add licence file to missing quickstarts

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2779: ----------------------------------- Summary: Add licence file to missing quickstarts Key: JBTM-2779 URL: https://issues.jboss.org/browse/JBTM-2779 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Tom Jenkinson Assignee: Amos Feng Fix For: 5.next There are a lot of quickstarts that do not have the expected licence declarations at the top of their files. You can find these: find . -type f | grep -v git | grep -v jar | grep -v tools | xargs grep -H -c 'Lesser\|LICENSE-2' | grep 0$ | cut -d':' -f1 | wc The correct licence should be added to them, you may find it easy to cat a licence file (in the correct .java, .xml, .sh, .bat format) to them. The licence is LGPL. Those that were originally ASL etc should remain that way. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2685: --------------------------------- It should download the Jigsaw ea release from https://jdk9.java.net/jigsaw to resolve this exception. > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2775) Upgrade byteman to 4.0.0-BETA0 to support the JDK 9

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2775?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2775: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade byteman to 4.0.0-BETA0 to support the JDK 9 > --------------------------------------------------- > > Key: JBTM-2775 > URL: https://issues.jboss.org/browse/JBTM-2775 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > This is a preview release allowing Byteman to be used with a JDK9 that includes the Java Platform Module System. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2778) Upgrade arquillian-container-karaf to 2.2.0.Final

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2778?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2778: --------------------------------- Thanks Tom > Upgrade arquillian-container-karaf to 2.2.0.Final > -------------------------------------------------- > > Key: JBTM-2778 > URL: https://issues.jboss.org/browse/JBTM-2778 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration, Build System > Reporter: Amos Feng > Assignee: Tom Jenkinson > Fix For: 5.next > > > The arquillian-container-karaf had release the 2.2.0.Final and it does not need to build the SNAPSHOT in the hudson/script/narayana.sh -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2016