September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13870) Upgrade to WildFly Core 13.0.0.Beta6

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13870?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-13870: ------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/13493) > Upgrade to WildFly Core 13.0.0.Beta6 > ------------------------------------ > > Key: WFLY-13870 > URL: https://issues.redhat.com/browse/WFLY-13870 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: James Perkins > Assignee: Jeff Mesnil > Priority: Major > Fix For: 21.0.0.Beta1 > > > Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/13.0.0.Beta5 > Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/13.0.0.Beta4...13.0.0.Beta5 > [Release notes|https://issues.redhat.com/secure/ConfigureReport.jspa?versions=1234...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13870) Upgrade to WildFly Core 13.0.0.Beta6

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-13870: ---------------------------------- Summary: Upgrade to WildFly Core 13.0.0.Beta6 Key: WFLY-13870 URL: https://issues.redhat.com/browse/WFLY-13870 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: James Perkins Assignee: James Perkins Fix For: 21.0.0.Beta1 Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/13.0.0.Beta5 Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/13.0.0.Beta4...13.0.0.Beta5 [Release notes|https://issues.redhat.com/secure/ConfigureReport.jspa?versions=1234...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13866) Several traces created in Jaeger for just one method call

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13866?page=com.atlassian.jira.plugi... ] Radoslav Husar commented on WFLY-13866: --------------------------------------- I am not that familiar with opentracing, but if it relies on thread local, that's not going to work in async case. [~lthon] can shed more light into the matter. > Several traces created in Jaeger for just one method call > --------------------------------------------------------- > > Key: WFLY-13866 > URL: https://issues.redhat.com/browse/WFLY-13866 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 21.0.0.Beta1 > Reporter: Fabio Burzigotti > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 21.0.0.Beta1 > > > I am migrating one opentracing/fault-tolerance test from Thorntail TS [1] and I noticed that Wildfly SNAPSHOT is behaving differently with respect to what in the subject. > The test is pretty simple, deploying a REST app which makes use of injected service which in turn leverages microprofile opentracing (via API) and fault-tolerance (via annotations). The test executes the following 2 methods in the given order: > - call {{hello}}, which is synchronous and is throwing an exception, hence failing and gets called again then ending up with the fallback. This generates 1 trace with 4 spans in Jaeger and the behavior is consistent between TT and WildFly > - call {{helloAsync}}, which is asynchronous and is throwing an exception, hence failing and getting called again (asynchronously?) then ending up with the fallback. This generates the following traces in Jaeger: > TT: 1 trace with 4 spans > WildFly: 4 separate traces , i.e. the one for the REST endpoint GET method, two for the {{helloAsync}} calls and one for the fallback. > [1] > https://github.com/rhoar-qe/thorntail-test-suite/tree/master/microprofile... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13869) Intermittent deployment failures in clustering testsuite

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13869: ----------------------------------- Summary: Intermittent deployment failures in clustering testsuite Key: WFLY-13869 URL: https://issues.redhat.com/browse/WFLY-13869 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: No Release Reporter: Paul Ferraro Assignee: Paul Ferraro e.g. [https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxMicroProfil...] Looks to be due to a blocked thread during start of the routing registry. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5644) [Test Scenario Editor] Queries should be not considered on RULE based Test Scenario

by Yeser Amer (Jira)

Yeser Amer created DROOLS-5644: ---------------------------------- Summary: [Test Scenario Editor] Queries should be not considered on RULE based Test Scenario Key: DROOLS-5644 URL: https://issues.redhat.com/browse/DROOLS-5644 Project: Drools Issue Type: Bug Affects Versions: 7.43.0.Final Reporter: Yeser Amer Assignee: Yeser Amer Fix For: 7.44.0.Final Running a Test Scenario, we expect to reach 100% test coverage. However, if the project contains DRL files with queries only, these files are counted in the coverage. As these files don't have any rule, it is not run and the test coverage is affected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5643) Consider isolating integration tests of DMN->PMML into specific module

by Jiri Petrlik (Jira)

[ https://issues.redhat.com/browse/DROOLS-5643?page=com.atlassian.jira.plug... ] Jiri Petrlik commented on DROOLS-5643: -------------------------------------- [~tari_manga] Thank you for creating this issue. Will look at it. > Consider isolating integration tests of DMN->PMML into specific module > ---------------------------------------------------------------------- > > Key: DROOLS-5643 > URL: https://issues.redhat.com/browse/DROOLS-5643 > Project: Drools > Issue Type: Task > Reporter: Matteo Mortari > Assignee: Jiri Petrlik > Priority: Major > > Please consider isolating the integration test for DMN->PMML > https://github.com/kiegroup/droolsjbpm-integration/tree/master/kie-server... > into their own test modules, please. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-355) Bootable JAR - scripts in bin folder of the server installation directory are not executable

by Tommaso Borgato (Jira)

[ https://issues.redhat.com/browse/WFWIP-355?page=com.atlassian.jira.plugin... ] Tommaso Borgato closed WFWIP-355. --------------------------------- > Bootable JAR - scripts in bin folder of the server installation directory are not executable > -------------------------------------------------------------------------------------------- > > Key: WFWIP-355 > URL: https://issues.redhat.com/browse/WFWIP-355 > Project: WildFly WIP > Issue Type: Bug > Reporter: Tommaso Borgato > Assignee: Jean Francois Denise > Priority: Major > > Related RFE: EAP7-1385 > Scripts in the bin folder of the server's installation directory are not executable; > If you start the server like the following: > {noformat} > java -jar target/default-hollow-jar-bootable.jar --install-dir=/tmp/wildfly-bootable-server-hollow-jar > {noformat} > and the look into the bin folder: > {noformat} > $ ls -ltr /tmp/wildfly-bootable-server-hollow-jar/bin > total 1520 > -rw-rw-r--. 1 hudson hudson 2362 Sep 11 10:11 vault.sh > -rw-rw-r--. 1 hudson hudson 709 Sep 11 10:11 vault.ps1 > -rw-rw-r--. 1 hudson hudson 2269 Sep 11 10:11 vault.bat > -rw-rw-r--. 1 hudson hudson 823 Sep 11 10:11 common.bat > -rw-rw-r--. 1 hudson hudson 1933 Sep 11 10:11 jboss-cli-logging.properties > -rw-rw-r--. 1 hudson hudson 3271 Sep 11 10:11 jboss-cli.bat > -rw-rw-r--. 1 hudson hudson 792 Sep 11 10:11 common.sh > -rw-rw-r--. 1 hudson hudson 11549 Sep 11 10:11 common.ps1 > -rw-rw-r--. 1 hudson hudson 893 Sep 11 10:11 jboss-cli.ps1 > -rw-rw-r--. 1 hudson hudson 1793 Sep 11 10:11 elytron-tool.sh > -rw-rw-r--. 1 hudson hudson 1079 Sep 11 10:11 elytron-tool.ps1 > -rw-rw-r--. 1 hudson hudson 1710 Sep 11 10:11 elytron-tool.bat > -rw-rw-r--. 1 hudson hudson 2392 Sep 11 10:11 add-user.sh > -rw-rw-r--. 1 hudson hudson 3035 Sep 11 10:11 jboss-cli.xml > -rw-rw-r--. 1 hudson hudson 2635 Sep 11 10:11 jboss-cli.sh > -rw-rw-r--. 1 hudson hudson 1069 Sep 11 10:11 add-user.ps1 > -rw-rw-r--. 1 hudson hudson 2444 Sep 11 10:11 add-user.properties > -rw-rw-r--. 1 hudson hudson 2417 Sep 11 10:11 add-user.bat > -rw-rw-r--. 1 hudson hudson 12843 Sep 11 10:11 standalone.sh > -rw-rw-r--. 1 hudson hudson 1624 Sep 11 10:11 standalone.ps1 > -rw-rw-r--. 1 hudson hudson 3226 Sep 11 10:11 standalone.conf.ps1 > -rw-rw-r--. 1 hudson hudson 3402 Sep 11 10:11 standalone.conf.bat > -rw-rw-r--. 1 hudson hudson 2965 Sep 11 10:11 standalone.conf > -rw-rw-r--. 1 hudson hudson 9576 Sep 11 10:11 standalone.bat > -rw-rw-r--. 1 hudson hudson 49 Sep 11 10:11 product.conf > -rw-rw-r--. 1 hudson hudson 49721 Sep 11 10:11 launcher.jar > -rw-rw-r--. 1 hudson hudson 1369074 Sep 11 10:11 wildfly-elytron-tool.jar > {noformat} > you can see e.g. jboss-cli.sh is not executable -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13866) Several traces created in Jaeger for just one method call

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13866?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13866: ------------------------------------------ The scope seems to be attached to a ThreadLocal but for some reason we get a new scope each time > Several traces created in Jaeger for just one method call > --------------------------------------------------------- > > Key: WFLY-13866 > URL: https://issues.redhat.com/browse/WFLY-13866 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 21.0.0.Beta1 > Reporter: Fabio Burzigotti > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 21.0.0.Beta1 > > > I am migrating one opentracing/fault-tolerance test from Thorntail TS [1] and I noticed that Wildfly SNAPSHOT is behaving differently with respect to what in the subject. > The test is pretty simple, deploying a REST app which makes use of injected service which in turn leverages microprofile opentracing (via API) and fault-tolerance (via annotations). The test executes the following 2 methods in the given order: > - call {{hello}}, which is synchronous and is throwing an exception, hence failing and gets called again then ending up with the fallback. This generates 1 trace with 4 spans in Jaeger and the behavior is consistent between TT and WildFly > - call {{helloAsync}}, which is asynchronous and is throwing an exception, hence failing and getting called again (asynchronously?) then ending up with the fallback. This generates the following traces in Jaeger: > TT: 1 trace with 4 spans > WildFly: 4 separate traces , i.e. the one for the REST endpoint GET method, two for the {{helloAsync}} calls and one for the fallback. > [1] > https://github.com/rhoar-qe/thorntail-test-suite/tree/master/microprofile... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-356) Operations :check (-live, -ready) not present in embedded and admin-only mode

by Martin Choma (Jira)

[ https://issues.redhat.com/browse/WFWIP-356?page=com.atlassian.jira.plugin... ] Martin Choma closed WFWIP-356. ------------------------------ Resolution: Done Thanks for explanation. Makes totally sense. > Operations :check (-live, -ready) not present in embedded and admin-only mode > ----------------------------------------------------------------------------- > > Key: WFWIP-356 > URL: https://issues.redhat.com/browse/WFWIP-356 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > microprofile-health-smallrye subsystem operations {{:check}}, {{check-live}}, {{check-ready}} not present in embedded or admin-only mode. Is this expected or we should move this jira to JBEAP bug? > Admin only mode > {code} > :reload(admin-only = true) > /subsystem=microprofile-health-smallrye:check > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0031: No operation named 'check' exists at address [(\"subsystem\" => \"microprofile-health-smallrye\")]", > "rolled-back" => true > } > {code} > Embedded mode > {code} > ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server > [standalone@embedded /] /subsystem=microprofile-health-smallrye:check-ready > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0031: No operation named 'check-ready' exists at address [(\"subsystem\" => \"microprofile-health-smallrye\")]", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13868) Eliminate dependency on org.jboss.as.security module from the vault-tool module

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13868: --------------------------------------- Summary: Eliminate dependency on org.jboss.as.security module from the vault-tool module Key: WFLY-13868 URL: https://issues.redhat.com/browse/WFLY-13868 Project: WildFly Issue Type: Sub-task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 21.0.0.Beta1 Although this is a PicketBox based tool it should not be directly depending on subsystem classes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020