September 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2886) Automatize XTS ssl quickstart to be tested in CI on Windows

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2886?page=com.atlassian.jira.plugin.... ] 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1719) Improve test coverage for REST-AT multiplexor.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1719?page=com.atlassian.jira.plugin.... ] 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1802) Consider moving Arquillian profiles to root pom.xml

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1802?page=com.atlassian.jira.plugin.... ] 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1507) Review the TXBridge tests usage of Arquillian

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1507?page=com.atlassian.jira.plugin.... ] 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2870) Provide way of getting suppressed exceptions out of SubordinateTransaction

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2870?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2870: ----------------------------------------------- Francesco Marchioni <fmarchio(a)redhat.com> 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3058) Add STM tests that verify nested transactions are closed

by Michael Musgrove (JIRA)

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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.... ] 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-dependenc...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2796) Investigate the Tomcat integration tests failure with the JDK 9

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2796?page=com.atlassian.jira.plugin.... ] 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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3057) build javadoc failure

by Amos Feng (JIRA)

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)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3057) build javadoc failure

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-3057?page=com.atlassian.jira.plugin.... ] 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)

5 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2018