June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled

by Claudio Weiler (Jira)

[ https://issues.jboss.org/browse/WFLY-11933?page=com.atlassian.jira.plugin... ] Claudio Weiler commented on WFLY-11933: --------------------------------------- Hi [~dlofthouse]! Nope, no user authenticated. But why any user or role assigned should play in this, as metrics, by default, are not protected in Wildfly: [https://docs.wildfly.org/17/Admin_Guide.html#management-model|https://doc...] > Error when accessing metrics with RBAC enabled > ---------------------------------------------- > > Key: WFLY-11933 > URL: https://issues.jboss.org/browse/WFLY-11933 > Project: WildFly > Issue Type: Bug > Components: Management, MP Metrics > Affects Versions: 16.0.0.Final, 17.0.0.Final > Reporter: Claudio Weiler > Assignee: Jeff Mesnil > Priority: Major > > When RBAC is enabled for management in Wildfly 16, metrics throws exception: > java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [ > ("subsystem" => "datasources"), > ("data-source" => "ExampleDS"), > ("statistics" => "pool") > ]: "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"ExampleDS\"), > (\"statistics\" => \"pool\") > ]' not found". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled

by Claudio Weiler (Jira)

[ https://issues.jboss.org/browse/WFLY-11933?page=com.atlassian.jira.plugin... ] Claudio Weiler edited comment on WFLY-11933 at 6/17/19 9:36 AM: ---------------------------------------------------------------- Hi [~dlofthouse]! Nope, no user authenticated, no roles. But why any user or role assigned should play in this, as metrics, by default, are not protected in Wildfly: [https://docs.wildfly.org/17/Admin_Guide.html#management-model|https://doc...] was (Author: cweiler): Hi [~dlofthouse]! Nope, no user authenticated. But why any user or role assigned should play in this, as metrics, by default, are not protected in Wildfly: [https://docs.wildfly.org/17/Admin_Guide.html#management-model|https://doc...] > Error when accessing metrics with RBAC enabled > ---------------------------------------------- > > Key: WFLY-11933 > URL: https://issues.jboss.org/browse/WFLY-11933 > Project: WildFly > Issue Type: Bug > Components: Management, MP Metrics > Affects Versions: 16.0.0.Final, 17.0.0.Final > Reporter: Claudio Weiler > Assignee: Jeff Mesnil > Priority: Major > > When RBAC is enabled for management in Wildfly 16, metrics throws exception: > java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [ > ("subsystem" => "datasources"), > ("data-source" => "ExampleDS"), > ("statistics" => "pool") > ]: "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"ExampleDS\"), > (\"statistics\" => \"pool\") > ]' not found". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled

by Claudio Weiler (Jira)

[ https://issues.jboss.org/browse/WFLY-11933?page=com.atlassian.jira.plugin... ] Claudio Weiler updated WFLY-11933: ---------------------------------- Affects Version/s: 17.0.0.Final > Error when accessing metrics with RBAC enabled > ---------------------------------------------- > > Key: WFLY-11933 > URL: https://issues.jboss.org/browse/WFLY-11933 > Project: WildFly > Issue Type: Bug > Components: Management, MP Metrics > Affects Versions: 16.0.0.Final, 17.0.0.Final > Reporter: Claudio Weiler > Assignee: Jeff Mesnil > Priority: Major > > When RBAC is enabled for management in Wildfly 16, metrics throws exception: > java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [ > ("subsystem" => "datasources"), > ("data-source" => "ExampleDS"), > ("statistics" => "pool") > ]: "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"ExampleDS\"), > (\"statistics\" => \"pool\") > ]' not found". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled

by Claudio Weiler (Jira)

[ https://issues.jboss.org/browse/WFLY-11933?page=com.atlassian.jira.plugin... ] Claudio Weiler updated WFLY-11933: ---------------------------------- Steps to Reproduce: 1. Install fresh Wildfly 16.0.0.Final Java EE Full & Web Distribution 2. Access metrics in localhost:9990/metrics. OK 3. Enable RBAC with jboss-cli: /core-service=management/access=authorization:write-attribute(name=provider,value=rbac) 4. Access metrics in localhost:9990/metrics. ERROR was: 1. Install fresh Wildfly 16.0.0.Final Java EE Full & Web Distribution 2. Enable RBAC with jboss-cli: /core-service=management/access=authorization:write-attribute(name=provider,value=rbac) 3. Access metrics in localhost:9990/metrics > Error when accessing metrics with RBAC enabled > ---------------------------------------------- > > Key: WFLY-11933 > URL: https://issues.jboss.org/browse/WFLY-11933 > Project: WildFly > Issue Type: Bug > Components: Management, MP Metrics > Affects Versions: 16.0.0.Final, 17.0.0.Final > Reporter: Claudio Weiler > Assignee: Jeff Mesnil > Priority: Major > > When RBAC is enabled for management in Wildfly 16, metrics throws exception: > java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [ > ("subsystem" => "datasources"), > ("data-source" => "ExampleDS"), > ("statistics" => "pool") > ]: "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"ExampleDS\"), > (\"statistics\" => \"pool\") > ]' not found". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4140) Global's method names starting with word modify are truncated

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4140?page=com.atlassian.jira.plugi... ] Luca Molteni resolved DROOLS-4140. ---------------------------------- Resolution: Done This was fixed here https://github.com/kiegroup/drools/commit/3ecc1d6e87e4822d44ce75ee0691340... Parsing of modify statements is done using a parser grammar rather than using String replace, so this kind of collision won't happen anymore. > Global's method names starting with word modify are truncated > ------------------------------------------------------------- > > Key: DROOLS-4140 > URL: https://issues.jboss.org/browse/DROOLS-4140 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.21.0.Final > Environment: FLOW_DSL, PATTERN_DSL > Reporter: Peter Martinovič > Assignee: Luca Molteni > Priority: Major > Attachments: DROOLS-4140-test.patch > > > If global's method name starts with modify, the first character of the method name is lost during code generation. > Compilation then fails. > {code:java} > org.drools.model.Rule rule = D.rule("Rule 1").build(D.on(var_g).execute((g) -> { > g.odifyIsTheFirstWordInTheMethodName(); > })); > {code} > (It does not seem to happen with method names starting with keywords insert, delete.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4189) Kogito Rules Getting Started

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4189: -------------------------------------- Summary: Kogito Rules Getting Started Key: DROOLS-4189 URL: https://issues.jboss.org/browse/DROOLS-4189 Project: Drools Issue Type: Task Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi Fix For: 8.0.0.Final add README.md / asciidoc about getting started with Drools inside Kogito -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4042) [DMN Designer] Add support for importing and consuming PMML models 7.5

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-4042?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-4042: --------------------------------------- [~jomarko] looks good, but a few more things to test: * included model aliases must be unique (doesn't matter if they are DMN or PMML includes) * if the PMML file contains no "named" model (only an anonymous one), the UI should indicate that this model is being used (how to indicate that I leave to UX, but we can call it "default model" or whatever). I [~manstis] is it possible to automatically update the document attribute on function definitions when a PMML model is renamed? I know it is something we don't do at the moment, but it would be nice if we could. > [DMN Designer] Add support for importing and consuming PMML models 7.5 > ---------------------------------------------------------------------- > > Key: DROOLS-4042 > URL: https://issues.jboss.org/browse/DROOLS-4042 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > > We need the ability to import PMML _documents_. This should be via the "Imported models" tab. Once a _document_ has been imported (and an alias assigned) selection of the _document_ and a _model_ held therein should be possible via the PMML Function boxed expression editor. > h2. Requirement > - As user, via included models tab, remove included pmml model, even if used somewhere > - As user, via included models tab, rename included pmml model, even if used somewhere > - As user, via included models tab, include multiple pmml models > - As user, via included models tab, include multiple pmml models at the same time eternal dmn > - As user, via included models tab, include multiple pmml models at the same time external dmn, kinds are visually distinguished > - As user, via dmn designer, if Document or Model of included pmml was changed, the lisboxes in dmn offers new values > - As user, via included models tab, no restriction for included pmml model name > - As user, via new test scenarios, test dmn model that uses pmml inside > - As user, via kie-server, query kie container that has dmn model with pmml > h2. UX design > - Selectbox in place of Document and Model selection > h2. Documentation > - Mention what pmml model can be imported into dmn > - Mention where it can be used > - Mention if something more needed to dpeloy such project on kie server > h2. Acceptance test > - Include two pmml models > - In dmn, select one in function grid > - Change the selected one to second > - Finish the dmn model > - build deploy on kie-server > - Interact with kie container via rest > - Create new test scenario for created dmn model -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3923?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3923: ----------------------------------- Story Points: 3 > (C)DI detection should be more reliable/standard for codegen > ------------------------------------------------------------ > > Key: DROOLS-3923 > URL: https://issues.jboss.org/browse/DROOLS-3923 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > we are currently doing {{ try { Class.forName("...ApplicationScoped") } }} which is > (1) pretty hackish (2) won't work in Maven because maven's ClassPath is not the same of the target application > We should rather use a config param or any better way to detect if we're going to use DI. Currently we have added a config param + "auto detect" using the technique above (in maven only the config param works) but auto-detect should be better. > Besides ApplicationScoped only work for CDI, while JSR-330 @Inject is independent from CDI so using ApplicationScoped as a signal is too limited. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1705) Audit remaining Class.forName in static factory methods

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1705?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-1705: ----------------------------------- Sprint: 2019 Week 23-25 > Audit remaining Class.forName in static factory methods > ------------------------------------------------------- > > Key: DROOLS-1705 > URL: https://issues.jboss.org/browse/DROOLS-1705 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Matteo Mortari > Assignee: Edoardo Vacchi > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3923?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3923: ----------------------------------- Sprint: 2019 Week 23-25 > (C)DI detection should be more reliable/standard for codegen > ------------------------------------------------------------ > > Key: DROOLS-3923 > URL: https://issues.jboss.org/browse/DROOLS-3923 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > we are currently doing {{ try { Class.forName("...ApplicationScoped") } }} which is > (1) pretty hackish (2) won't work in Maven because maven's ClassPath is not the same of the target application > We should rather use a config param or any better way to detect if we're going to use DI. Currently we have added a config param + "auto detect" using the technique above (in maven only the config param works) but auto-detect should be better. > Besides ApplicationScoped only work for CDI, while JSR-330 @Inject is independent from CDI so using ApplicationScoped as a signal is too limited. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019