January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5122) SceSim is not clearing alert after update, successful Save and re Run

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5122?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5122: ------------------------------- Fix Version/s: 7.49.0.Final > SceSim is not clearing alert after update, successful Save and re Run > --------------------------------------------------------------------- > > Key: DROOLS-5122 > URL: https://issues.redhat.com/browse/DROOLS-5122 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Matteo Mortari > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Fix For: 7.49.0.Final > > Attachments: Screenshot 2020-03-03 at 15.36.33.png > > > as attached -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFWIP-369) EAP metrics are shown on Metrics dashboard but not from linked Prometheus UI in OCP web console

by Jan Kasik (Jira)

[ https://issues.redhat.com/browse/WFWIP-369?page=com.atlassian.jira.plugin... ] Jan Kasik moved CLOUD-3880 to WFWIP-369: ---------------------------------------- Component/s: OpenShift (was: EAP7) Key: WFWIP-369 (was: CLOUD-3880) Affects Version/s: (was: EAP73 7.3.7.GA) Workflow: GIT Pull Request workflow (was: CDW v1) Project: WildFly WIP (was: Cloud Enablement) > EAP metrics are shown on Metrics dashboard but not from linked Prometheus UI in OCP web console > ----------------------------------------------------------------------------------------------- > > Key: WFWIP-369 > URL: https://issues.redhat.com/browse/WFWIP-369 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Kasik > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > The Prometheus instance linked to "Prometheus UI" link is not able to query metrics from EAP. If this intentional, the integration and user experience is flawed because users can be confused since the link is not labeled properly. > This is a bug in integration of Prometheus, OpenShift and EAP. > cc [~jdenise] -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14298) Using fault-tolerance in Wildfly 22 causes WELD-001408

by sdfsd fsdfsdf (Jira)

sdfsd fsdfsdf created WFLY-14298: ------------------------------------ Summary: Using fault-tolerance in Wildfly 22 causes WELD-001408 Key: WFLY-14298 URL: https://issues.redhat.com/browse/WFLY-14298 Project: WildFly Issue Type: Bug Components: EE Affects Versions: 22.0.0.Final Reporter: sdfsd fsdfsdf Assignee: Brian Stansberry In wildfly 21, I used to put these lines into the standalone-full-ha.xml: <extension module="org.wildfly.extension.microprofile.fault-tolerance-smallrye"/> ... <subsystem xmlns="urn:wildfly:microprofile-fault-tolerance-smallrye:1.0"/> If I put those lines into the standalone-full-ha.xml of Wildfly 22 I get the following error when deploying an appliction that uses fault-tolerance: WELD-001408: Unsatisfied dependencies for type MetricRegistry with qualifiers @Default @Inject io.smallrye.faulttolerance.metrics.MetricsCollectorFactory.registry I already have these lines in the standalone: <extension module="org.wildfly.extension.metrics"/> <extension module="org.wildfly.extension.health"/> Is there something else I need to add in the standalone in order to keep using fault-tolerance in Wildfly 22? -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14297) Admin Guide refers EE Managed Executors core-threads attribute as mandatory

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-14297: -------------------------------------- Summary: Admin Guide refers EE Managed Executors core-threads attribute as mandatory Key: WFLY-14297 URL: https://issues.redhat.com/browse/WFLY-14297 Project: WildFly Issue Type: Bug Components: Concurrency Utilities Affects Versions: 22.0.0.Final Reporter: Eduardo Martins Assignee: Eduardo Martins ... The attribute is optional, when not provided the value is automatically computed. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5911) It's not possible to save arrow edits on DMN Editor

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5911?page=com.atlassian.jira.plug... ] Guilherme Gomes commented on DROOLS-5911: ----------------------------------------- Hi [~roger600], as this is not a blocker, I would leave the fix for 7.11. However, let's see what [~davidredhat] thinks. > It's not possible to save arrow edits on DMN Editor > --------------------------------------------------- > > Key: DROOLS-5911 > URL: https://issues.redhat.com/browse/DROOLS-5911 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.48.0.Final > Reporter: Wagner Lemos > Assignee: Wagner Lemos > Priority: Major > Labels: Stunner, kogito, kogito-tooling > > On the DMN Editor, making a change on the arrow that connects two nodes isn't being saved. An example of change is moving the rear or tip of the arrow to another side of the node -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5937) Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL.

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5937?page=com.atlassian.jira.plug... ] Toshiya Kobayashi edited comment on DROOLS-5937 at 1/15/21 5:24 AM: -------------------------------------------------------------------- Drools test case is covered by [https://github.com/kiegroup/drools/commit/f6449da5bda23fe5f44b92e55b39668...] (shared with DROOLS-5897) was (Author: tkobayashi): Drools test case is covered by https://github.com/kiegroup/drools/commit/f6449da5bda23fe5f44b92e55b39668... > Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL. > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5937 > URL: https://issues.redhat.com/browse/DROOLS-5937 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.48.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: support > Fix For: 7.49.0.Final > > Attachments: reproducer_02801729_6_mvel.zip, reproducer_02801729_6e_6f.zip > > > Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL (org.mvel2). > When using MVEL.eval method, the result of "+=" operation is incorrect, and "-=", "*=", "/=" operations result in an error. > - BigDecimal_type_property <op> Numeric_value (Initial value of $bus.weight is 12000B) > -- $bus.weight += 1000 ==> 1000 // incorrect result > -- $bus.weight -= 1000 ==> Error > -- $bus.weight *= 1000 ==> Error > -- $bus.weight /= 1000 ==> Error > - BigDecimal_type_property <op> BigDecimal_value (Initial value of $bus.weight and bdv are 12000B and 1000B respectively) > -- $bus.weight += bdv ==> 1000 // incorrect result > -- $bus.weight -= bdv ==> Error > -- $bus.weight *= bdv ==> Error > -- $bus.weight /= bdv ==> Error > When using MVEL.executeExpression method, the result of "+=" operation is correct, while "-=", "*=", "/=" operations cause an error. > - BigDecimal_type_property <op> Numeric_value (Initial value of $bus.weight is 12000B) > -- $bus.weight += 1000 ==> 13000 // correct > -- $bus.weight -= 1000 ==> Error > -- $bus.weight *= 1000 ==> Error > -- $bus.weight /= 1000 ==> Error > - BigDecimal_type_property <op> BigDecimal_value (Initial value of $bus.weight and bdv are 12000B and 1000B respectively) > -- $bus.weight += bdv ==> 13000 // correct > -- $bus.weight -= bdv ==> Error > -- $bus.weight *= bdv ==> Error > -- $bus.weight /= bdv ==> Error > $bus.weight is a BigDecimal type property. > MVEL library should return correct result for any operations above. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13011) The quickstart template appears out of date

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13011?page=com.atlassian.jira.plugi... ] Eduardo Martins resolved WFLY-13011. ------------------------------------ Resolution: Out of Date The updated doc plugin does not throws NPEs on null technologies. > The quickstart template appears out of date > ------------------------------------------- > > Key: WFLY-13011 > URL: https://issues.redhat.com/browse/WFLY-13011 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 19.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Eduardo Martins > Priority: Major > > The quickstart template appears to be out of date based on the present requirements. > One example it does not contain the technologies attribute which leads to a NullPointerException when building the docs with a new quickstart using the template. > Additionally later quickstarts appear to use an abstract differently to how the template describes them to define some more values so it would be nice to see some description of how this should be used. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5948) Compiled Alpha Network generation fails when we have the startsWith constraint before the indexed constraint age == index

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5948: ------------------------------------ Summary: Compiled Alpha Network generation fails when we have the startsWith constraint before the indexed constraint age == index Key: DROOLS-5948 URL: https://issues.redhat.com/browse/DROOLS-5948 Project: Drools Issue Type: Bug Components: core engine Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14296) Reenable ignored metrics tests

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-14296?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFLY-14296: ------------------------------ Description: https://issues.redhat.com/browse/WFLY-14206 / https://github.com/wildfly/wildfly/pull/13883 ignores a test. We need to reenable this before WF23 (was: R) > Reenable ignored metrics tests > ------------------------------ > > Key: WFLY-14296 > URL: https://issues.redhat.com/browse/WFLY-14296 > Project: WildFly > Issue Type: Task > Components: MP Metrics > Reporter: Kabir Khan > Assignee: Jason Lee > Priority: Blocker > Fix For: 23.0.0.Beta1 > > > https://issues.redhat.com/browse/WFLY-14206 / https://github.com/wildfly/wildfly/pull/13883 ignores a test. We need to reenable this before WF23 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14296) Reenable ignored metrics tests

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-14296?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFLY-14296: ------------------------------ Priority: Blocker (was: Major) > Reenable ignored metrics tests > ------------------------------ > > Key: WFLY-14296 > URL: https://issues.redhat.com/browse/WFLY-14296 > Project: WildFly > Issue Type: Task > Components: MP Metrics > Reporter: Kabir Khan > Assignee: Jason Lee > Priority: Blocker > > R -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021