December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFWIP-287: -------------------------------------- [~rhusar] I've added a reproducer. Note that it will fail in 50% of cases as it's random which module from EAR gets loaded. > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Miroslav Novak updated WFWIP-287: --------------------------------- Steps to Reproduce: *NOT 100% reproducer will it issue in 50% of run as it's random which MP FT module from EAR gets loaded* Steps to reproduce: * Build Wildfly with MP FT: ** https://github.com/rhusar/wildfly/tree/WFLY-12590 ** Commit: 3ff9787ca147a45c1651fe1946b02c07c0a6ad15 * Run the test by (provide path to build Wildfly server): {code} git clone git@github.com:mnovak1/eap-microprofile-test-suite.git cd eap-microprofile-test-suite mvn clean verify -DfailIfNoTests=false -Darquillian.deploymentExportPath=target/deployments/ -Djboss.home=$WILDFLY_HOME -P mp-ft -Dtest=MultipleFaultToleranceModuleEarTest#testFirstModuleConfiguresHystrix {code} > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFWIP-287: -------------------------------------- [~mnovak] Please link the test case in steps to reproduce. > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1034) Wizard - 3scale API Management Rule

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1034?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1034: ---------------------------------- Sprint: Kiali Sprint #30 > Wizard - 3scale API Management Rule > ----------------------------------- > > Key: SWSQE-1034 > URL: https://issues.redhat.com/browse/SWSQE-1034 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > > Automate CRUD scenario. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1036) Adjust tests https://github.com/kiali/kiali/issues/1474

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1036?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1036: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/228 > Adjust tests https://github.com/kiali/kiali/issues/1474 > ------------------------------------------------------- > > Key: SWSQE-1036 > URL: https://issues.redhat.com/browse/SWSQE-1036 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1036) Adjust tests https://github.com/kiali/kiali/issues/1474

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1036?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1036. ----------------------------------- Assignee: Hayk Hovsepyan Resolution: Done > Adjust tests https://github.com/kiali/kiali/issues/1474 > ------------------------------------------------------- > > Key: SWSQE-1036 > URL: https://issues.redhat.com/browse/SWSQE-1036 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4871) Complex value list doesn't work in guided rule editor

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4871?page=com.atlassian.jira.plug... ] Toni Rikkola moved RHPAM-2587 to DROOLS-4871: --------------------------------------------- Project: Drools (was: Red Hat Process Automation Manager) Key: DROOLS-4871 (was: RHPAM-2587) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: Guided Rule Editor (was: Business Central) Affects Build: (was: CR1) Affects Version/s: (was: 7.5.0.GA) QE Status: NEW > Complex value list doesn't work in guided rule editor > ----------------------------------------------------- > > Key: DROOLS-4871 > URL: https://issues.redhat.com/browse/DROOLS-4871 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > This issue was found during RHPAM-2323 review. It is slightly different however related. > The issue can be spotted on multiple places: > - Guided Rule > - Guided Rule Template > - Guided Decision Table - BRL condition fragment > If user wants to define constraint with operator *is contained in ([list of values])* then there is issue if the *[list of values]* is complex - it contains additional quotes or brackets. > h2. Reproducer Test > https://github.com/kiegroup/drools/pull/2588 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4763) interface "any" tag not working as expected

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFCORE-4763?page=com.atlassian.jira.plug... ] Kabir Khan commented on WFCORE-4763: ------------------------------------ [~brian.stansberry] I merged your PR. I think this Jira should be resolved but am not 100% sure so I will leave that to you. > interface "any" tag not working as expected > ------------------------------------------- > > Key: WFCORE-4763 > URL: https://issues.redhat.com/browse/WFCORE-4763 > Project: WildFly Core > Issue Type: Bug > Components: Management > Environment: Ubuntu 18.02 > Reporter: Yann Le Tallec > Priority: Major > > The {{<any>}} tag in the {{interface}} configuration of {{standalone.xml}} should accept any connection that matches ANY of the provided rules. This is not the case as demonstrated by the example below. > This configuration allows to run {{jboss-cli.sh -c}} from the machine where wildfly is running as expected: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > </any> > </interface> > </interfaces> > {code} > But if I add another (VALID) IP address inside the any tag, I can't connect any more: > {code:xml} > <interfaces> > <interface name="management"> > <any> > <inet-address value="127.0.0.1"/> > <inet-address value="10.20.230.26"/> > </any> > </interface> > </interfaces> > {code} > With the latter configuration, {{connect}} fails with the following error: > {noformat} > >The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused > {noformat} > Note: to easily reproduce the problem from the cli, starting from a fresh standalone install: > {code:bash} > connect > /interface=management:undefine-attribute(name=inet-address) > /interface=management:undefine-attribute(name=any) > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1]}) > reload > /interface=management:write-attribute(name=any,value={inet-address=[127.0.0.1,10.20.230.26]}) > reload > {code} > Notes: > - 10.20.230.26 must be a reachable IP - if I use a random one I can connect normally. > - if I use {{subnet-match}} I get the same issue -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4724?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-4724: ---------------------------------------- Sorry I missed these notifications. I will work to make WARN consistent with Optional, Error consistent with mandatory. > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.redhat.com/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-11-29 12-04-18.png, error.log, image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png, m.dmn, save-context.webm, screenshot-1.png, screenshot-2.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. > h2. Manual acceptance test > Try to save default / empty > h3. Business Central > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation > h3. Kogito > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4724?page=com.atlassian.jira.plug... ] Michael Anstis edited comment on DROOLS-4724 at 12/13/19 8:02 AM: ------------------------------------------------------------------ [~tari_manga] Could you please advise on my comment above, summarised here? IMO {{dmn-core}}\(?) may need some changes to make reporting of invalid BKM state consistent (message from {{dmn-validation}} and {{KieBuilder}}). {quote} ERROR - DMN: Missing expression for Business Knowledge Model node WARNING - \[KBase: defaultKieBase\]: DMN: Missing expression for Business Knowledge Model node {quote} The first line is from presumably {{dmn-validation}} the second from {{KieBuilder}}. was (Author: manstis): [~tari_manga] Could you please advise on my comment above, summarised here? IMO {{dmn-core}}\(?) may need some changes to make reporting of invalid BKM state consistent (message from {{dmn-validation}} and {{KieBuilder}}). {quote} ERROR - DMN: Missing expression for Business Knowledge Model node WARNING - \[KBase: defaultKieBase\]: DMN: Missing expression for Business Knowledge Model node {quote} The first line is from presumably `dmn-validation` the second from `KieBuilder`. > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.redhat.com/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-11-29 12-04-18.png, error.log, image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png, m.dmn, save-context.webm, screenshot-1.png, screenshot-2.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. > h2. Manual acceptance test > Try to save default / empty > h3. Business Central > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation > h3. Kogito > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019