From issues at jboss.org Mon Sep 3 04:14:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 3 Sep 2018 04:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3055) Clarify title of the manual which describes functionality available in a known product In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3055: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Clarify title of the manual which describes functionality available in a known product > -------------------------------------------------------------------------------------- > > Key: JBTM-3055 > URL: https://issues.jboss.org/browse/JBTM-3055 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Fix For: 5.next > > > Currently the manual states "Narayana Product Documentation" whereas in fact that section of documentation describes the functionality that is available in the Red Hat JBoss EAP product. The manual title could be clearer here. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Sep 4 10:19:01 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 4 Sep 2018 10:19:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3056) Remove the xts-test-servlet dependency in narayana-full In-Reply-To: References: Message-ID: Amos Feng created JBTM-3056: ------------------------------- Summary: Remove the xts-test-servlet dependency in narayana-full Key: JBTM-3056 URL: https://issues.jboss.org/browse/JBTM-3056 Project: JBoss Transaction Manager Issue Type: Task Components: XTS Reporter: Amos Feng Assignee: Amos Feng this dependency is generated by the module XTS/WSAS/xts-test-servlet but does not produce any files. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Sep 6 03:30:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 6 Sep 2018 03:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2851) Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng resolved JBTM-2851. ----------------------------- Resolution: Done upgrade openjdk-orb to 8.0.0.Final > Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) > ------------------------------------------------------------------------------ > > Key: JBTM-2851 > URL: https://issues.jboss.org/browse/JBTM-2851 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > > The blacktie-admin-service-ear is failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. > So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. > [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html > [2] https://github.com/jboss/openjdk-orb/pull/4 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Sep 6 03:30:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 6 Sep 2018 03:30:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2851) Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng closed JBTM-2851. --------------------------- > Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) > ------------------------------------------------------------------------------ > > Key: JBTM-2851 > URL: https://issues.jboss.org/browse/JBTM-2851 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > > The blacktie-admin-service-ear is failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. > So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. > [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html > [2] https://github.com/jboss/openjdk-orb/pull/4 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Sep 6 03:33:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 6 Sep 2018 03:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3057) build javadoc failure In-Reply-To: References: Message-ID: Amos Feng created JBTM-3057: ------------------------------- Summary: build javadoc failure Key: JBTM-3057 URL: https://issues.jboss.org/browse/JBTM-3057 Project: JBoss Transaction Manager Issue Type: Sub-task Reporter: Amos Feng Assignee: Amos Feng I have to disable the maven-javadoc-plugin on the JDK9 and it needs more investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Sep 6 03:33:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 6 Sep 2018 03:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3057) build javadoc failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-3057: ---------------------------- Component/s: Build System > build javadoc failure > --------------------- > > Key: JBTM-3057 > URL: https://issues.jboss.org/browse/JBTM-3057 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > > I have to disable the maven-javadoc-plugin on the JDK9 and it needs more investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Sep 6 03:42:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 6 Sep 2018 03:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2796) Investigate the Tomcat integration tests failure with the JDK 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629656#comment-13629656 ] Amos Feng commented on JBTM-2796: --------------------------------- The arquillian-container-tomcat has the new release 1.1.0.Final to support JDK9. So we need to upgrade in https://github.com/web-servers/narayana-tomcat/issues/20 > Investigate the Tomcat integration tests failure with the JDK 9 > --------------------------------------------------------------- > > Key: JBTM-2796 > URL: https://issues.jboss.org/browse/JBTM-2796 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Application Server Integration, Build System > Reporter: Amos Feng > Assignee: Amos Feng > Labels: jdk9 > > Endorsed standards and standalone APIs > in modular form will be supported via the concept of upgradeable modules -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Sep 6 03:53:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 6 Sep 2018 03:53:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng closed JBTM-2992. --------------------------- Resolution: Out of Date > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Sun Sep 9 12:57:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sun, 9 Sep 2018 12:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3058) Add STM tests that verify nested transactions are closed In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-3058: -------------------------------------- Summary: Add STM tests that verify nested transactions are closed Key: JBTM-3058 URL: https://issues.jboss.org/browse/JBTM-3058 Project: JBoss Transaction Manager Issue Type: Bug Components: STM Affects Versions: 5.9.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.next STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions are closed. STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "Tips on how to evaluate STM implementations" -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Sep 12 11:58:00 2018 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 12 Sep 2018 11:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2870) Provide way of getting suppressed exceptions out of SubordinateTransaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632555#comment-13632555 ] RH Bugzilla Integration commented on JBTM-2870: ----------------------------------------------- Francesco Marchioni changed the Status of [bug 1459824|https://bugzilla.redhat.com/show_bug.cgi?id=1459824] from NEW to CLOSED > Provide way of getting suppressed exceptions out of SubordinateTransaction > -------------------------------------------------------------------------- > > Key: JBTM-2870 > URL: https://issues.jboss.org/browse/JBTM-2870 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 4.17.38, 5.5.5.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 4.17.40, 5.2.23.Final, 5.5.7.Final, 5.6.0.Final > > > We need to provide way how to pass suppressed exceptions of of the `SubordinateTransaction` to the caller. > This request came from customer case and https://bugzilla.redhat.com/show_bug.cgi?id=1435549 as we need to provide exceptions thrown from transaction resource. > The interface is used for controlling propagated transaction from one server to another in EAP/WFLY. > Callers are is ejb3 subsystem in EAP 6.4/7.0 and WFTC in EAP 7.1. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Sep 14 06:10:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Sep 2018 06:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1719) Improve test coverage for REST-AT multiplexor. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1719: -------------------------------- Issue Type: Task (was: Enhancement) > Improve test coverage for REST-AT multiplexor. > ---------------------------------------------- > > Key: JBTM-1719 > URL: https://issues.jboss.org/browse/JBTM-1719 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Implement more unit and integration tests to cover more aspects of multiplexor functionality (https://github.com/jbosstm/narayana/tree/master/rts/at/integration). Especially recovery. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Sep 14 06:10:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Sep 2018 06:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1802) Consider moving Arquillian profiles to root pom.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1802: -------------------------------- Issue Type: Task (was: Enhancement) > Consider moving Arquillian profiles to root pom.xml > --------------------------------------------------- > > Key: JBTM-1802 > URL: https://issues.jboss.org/browse/JBTM-1802 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Testing > Reporter: Paul Robinson > Priority: Minor > > We have three Arquillian profiles (for managed, remote and ipv6-managed) present in the pom of nearly every test that uses Arquillian. I suspect they can all be identical and thus placed int he root pom.xml. This should simplify maintenance and will ensure any fixes to this config are made throughout. > The problem is that we may have legitimate reasons for this config to differ for some tests. Maybe we could use overrides in these cases. > Assigning to Tom for his input. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Sep 14 06:10:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Sep 2018 06:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1507) Review the TXBridge tests usage of Arquillian In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1507: -------------------------------- Issue Type: Task (was: Enhancement) > Review the TXBridge tests usage of Arquillian > --------------------------------------------- > > Key: JBTM-1507 > URL: https://issues.jboss.org/browse/JBTM-1507 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, TxBridge > Reporter: Paul Robinson > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > The TXBridge tests don;t seem to be using Arquillian correctly. There is a servlet that is invoked to do things inside the container. As the tests (should) now run in the container, this should not be needed. > The tests also seem to have added complexity due to the recovery tests. As the recovery tests need to be able to kill the container, it mandates manual container lifecycle management for *all* tests. We may want to pull out the recovery tests into a separate module. > We also may want to pull out the DisabledContextPropagationTest into a separate module as they use a modified AS configuration. > We should also take a general look at how the tests are structured and using Arq. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Sep 14 06:11:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Sep 2018 06:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2478) Use Flame Graph tool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2478: -------------------------------- Issue Type: Task (was: Enhancement) > Use Flame Graph tool > -------------------- > > Key: JBTM-2478 > URL: https://issues.jboss.org/browse/JBTM-2478 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Priority: Optional > > Tools and instructions are at: > https://github.com/jesperpedersen/perfjava/ <-- CPU sampling > https://github.com/jesperpedersen/javamemflame <-- Memory allocation tracking > Both use Agent_OnLoad/Agent_OnUnload, so better for smaller tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Sep 14 06:11:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Sep 2018 06:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2788) TestGroup_txcore is missing from the documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2788: -------------------------------- Issue Type: Bug (was: Enhancement) > TestGroup_txcore is missing from the documentation > -------------------------------------------------- > > Key: JBTM-2788 > URL: https://issues.jboss.org/browse/JBTM-2788 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Affects Versions: 5.3.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > > The [narayana QA test suite documentation |http://narayana.io//docs/project/index.html#d0e18351] is missing a description of the tests in the TestGroup_txcore group. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Sep 14 06:11:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 14 Sep 2018 06:11:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2886) Automatize XTS ssl quickstart to be tested in CI on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2886: -------------------------------- Issue Type: Task (was: Enhancement) > Automatize XTS ssl quickstart to be tested in CI on Windows > ----------------------------------------------------------- > > Key: JBTM-2886 > URL: https://issues.jboss.org/browse/JBTM-2886 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.2 > Reporter: Ondra Chaloupka > > There was created a shell script for JBTM-2882 which automatize testing of XTS over SSL. The steps were already written in `README.md` but that was not run automatically on CI. > The linux version with shell script was provided but we need windows version with `.bat`. This is a followup task to provide the bat script for the automatization on Windows. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Sep 14 09:20:01 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 14 Sep 2018 09:20:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3058) Add STM tests that verify nested transactions are closed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3058: ----------------------------------- Description: STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions follow the closed model. Furthermore, STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "[Tips on how to evaluate STM implementations|http://example.com|https://jbossts.blogspot.com/2018/09/tips-on-how-to-evaluate-stm.html]" was: STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions are closed. STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "Tips on how to evaluate STM implementations" > Add STM tests that verify nested transactions are closed > -------------------------------------------------------- > > Key: JBTM-3058 > URL: https://issues.jboss.org/browse/JBTM-3058 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions follow the closed model. > Furthermore, STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. > Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "[Tips on how to evaluate STM implementations|http://example.com|https://jbossts.blogspot.com/2018/09/tips-on-how-to-evaluate-stm.html]" -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Sep 19 12:26:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 19 Sep 2018 12:26:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3059) Move the JAX-RS specific parts of the LRA API into a separate API In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-3059: -------------------------------------- Summary: Move the JAX-RS specific parts of the LRA API into a separate API Key: JBTM-3059 URL: https://issues.jboss.org/browse/JBTM-3059 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next To ensure that the LRA APIs have broader applicability the JAX-RS specific aspects of the API need to be pulled out into a separate section. This change will mean it is possible to provide implementations of the API using non JAX-RS transports (such as gRPC etc). -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Sep 20 07:40:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 20 Sep 2018 07:40:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3060) Enhance quickstart readme with summary of all quickstarts while sorting them into categories In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-3060: ------------------------------------- Summary: Enhance quickstart readme with summary of all quickstarts while sorting them into categories Key: JBTM-3060 URL: https://issues.jboss.org/browse/JBTM-3060 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor The current README of the quickstart repository https://github.com/jbosstm/quickstart/blob/5.9.0.Final/README.md is a bit modest. Any stranger should get information about the overall structure of the repo while guiding him to find the quickstart he needs. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Sep 21 03:35:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 21 Sep 2018 03:35:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3060) Enhance quickstart readme with summary of all quickstarts while sorting them into categories In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636642#comment-13636642 ] Ondra Chaloupka commented on JBTM-3060: --------------------------------------- It seems there is a bit more work on this. Some quickstarts do not work with WildFly at all. There is need be done maintanance. > Enhance quickstart readme with summary of all quickstarts while sorting them into categories > -------------------------------------------------------------------------------------------- > > Key: JBTM-3060 > URL: https://issues.jboss.org/browse/JBTM-3060 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > The current README of the quickstart repository https://github.com/jbosstm/quickstart/blob/5.9.0.Final/README.md is a bit modest. Any stranger should get information about the overall structure of the repo while guiding him to find the quickstart he needs. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Sep 24 06:50:00 2018 From: issues at jboss.org (Jiri Ondrusek (JIRA)) Date: Mon, 24 Sep 2018 06:50:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3061) CMR recovery wrongly handles commit and rollback In-Reply-To: References: Message-ID: Jiri Ondrusek created JBTM-3061: ----------------------------------- Summary: CMR recovery wrongly handles commit and rollback Key: JBTM-3061 URL: https://issues.jboss.org/browse/JBTM-3061 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.8.1.Final Reporter: Jiri Ondrusek Assignee: Ondra Chaloupka Fix For: 5.9.0.Final The recovery of CMR works wrongly. For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. # cmr resource prepare (no real action on the local transction) # xa resource prepare (prepared in real as XA) # cmr resource commit (commiting the local transaction) # JVM crash # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Sep 24 06:56:00 2018 From: issues at jboss.org (Jiri Ondrusek (JIRA)) Date: Mon, 24 Sep 2018 06:56:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3061) CMR recovery wrongly handles commit and rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek updated JBTM-3061: -------------------------------- Fix Version/s: (was: 5.9.0.Final) Affects Version/s: 5.5.32.Final (was: 5.8.1.Final) > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3061 > URL: https://issues.jboss.org/browse/JBTM-3061 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.32.Final > Reporter: Jiri Ondrusek > Assignee: Ondra Chaloupka > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Sep 24 06:57:00 2018 From: issues at jboss.org (Jiri Ondrusek (JIRA)) Date: Mon, 24 Sep 2018 06:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3061) CMR recovery wrongly handles commit and rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek reassigned JBTM-3061: ----------------------------------- Assignee: Jiri Ondrusek (was: Ondra Chaloupka) > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3061 > URL: https://issues.jboss.org/browse/JBTM-3061 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.32.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Sep 24 06:57:00 2018 From: issues at jboss.org (Jiri Ondrusek (JIRA)) Date: Mon, 24 Sep 2018 06:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3061) CMR recovery wrongly handles commit and rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek updated JBTM-3061: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1366 (was: https://github.com/jbosstm/narayana/pull/1343) > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3061 > URL: https://issues.jboss.org/browse/JBTM-3061 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.32.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)