November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3228) Rules don't produce the correct result anymore after a session reset

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3228?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-3228: ------------------------------------- Poker: 3 > Rules don't produce the correct result anymore after a session reset > -------------------------------------------------------------------- > > Key: DROOLS-3228 > URL: https://issues.jboss.org/browse/DROOLS-3228 > Project: Drools > Issue Type: Bug > Affects Versions: 7.13.0.Final > Reporter: Christian Liebhardt > Assignee: Mario Fusco > Priority: Major > > Hello, > A while ago I've created a test project to compare the different possibilities of session types and session polling/reusing. After an update to Drools 7.13.0.Final I found a performance improvement but also three issues. I would summarize all issues in this ticket, let me know if you have a different preference. I have also created a PR which helped me to continue with my tests: https://github.com/kiegroup/drools/pull/2135 > *1. Incorrect results* > If you clone the project and execute [StatefulDroolsEngineUnitTest.java|https://github.com/liebharc/JavaRules/b...] then you will see test failures with 7.13.0.Final while the tests pass with 7.12.0.Final. I could trace the issue back to a recent change in ConcurrentNodeMemories. If I revert this change on a snapshot build of 7.14.0 then the tests pass again. > *2. Reset doesn't bring a disposed session back to life* > With 7.12.0.Final it was possible to bring a disposed session back to life by calling the reset method. In 7.13.0.Final that doesn't work anymore because the checkAlive validation then fails. > The new session pools seem to deal with that by just setting the alive flag back to true if a session is reused. While the new session pools are great, we would like to stick with our existing and simpler session pooling which makes use of the reset method. So would it be possible to set the alive flag to true on a session reset? > *3. A stateless sequential session doesn't execute any rules after a reset* > https://github.com/liebharc/JavaRules/blob/master/src/test/java/com/githu... fails as a stateless sequential session skips all adds to its agenda group queue after the session has been reset. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3236) Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3236?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-3236: ---------------------------------------- I found https://stackoverflow.com/a/52984814/893991 on SO with the same problem. Once this is fixed would be nice to post a link to the final solution also there. > Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter" > ------------------------------------------------------------------------------------------- > > Key: DROOLS-3236 > URL: https://issues.jboss.org/browse/DROOLS-3236 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 7.10.0.Final, 7.11.0.Final, 7.12.0.Final, 7.13.0.Final > Environment: Eclipse photon, Eclipse 2018 09, no special plugin > m2eclipse configured to do-not-manage/ignore any unknown plugin goal (easiest choice) > Reporter: Matteo Mortari > Assignee: Mario Fusco > Priority: Major > Attachments: image-2018-11-05-10-28-50-255.png > > > Since 7.10.0.Final the following error occurs when opening a KJAR project in Eclipse: > !image-2018-11-05-10-28-50-255.png! > Errors occurred during the build. > Errors running builder 'Maven Project Builder' on project '...'. > Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals must be specificed, but found: groupId = 'org.kie' > artifactId = 'kie-maven-plugin' > versionRange = '7.10.0.Final' > goals = '[]' > Please notice kie-maven-plugin 7.9.0.Final and earlier do NOT exhibit this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-127) Subsystem jgroups exposes 354 metrics, no way to expose subset of metrics

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFWIP-127?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFWIP-127: ----------------------------------------- Description of the issues says: {{There is no way to expose subset of metrics for subsystem}}. In case of jgroups subsystem it's not sufficient for me to have 0 or 354. I would like to specify just some of the jgroups metrics ... Or other way around is to *expose just 10-20 metrics for jgroups*. Who will really look into that? It's just too low level information and jgroups are just implementation detail and modules.xml for org.jgroups says {{<property name="jboss.api" value="unsupported"/>}} When I look into Prometheus and create new chart, drop-down list is polluted by jgroups items which are more than 70% of all the entries in the list. > Subsystem jgroups exposes 354 metrics, no way to expose subset of metrics > ------------------------------------------------------------------------- > > Key: WFWIP-127 > URL: https://issues.jboss.org/browse/WFWIP-127 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > Subsystem jgroups exposes 354 metrics > There is no way to expose subset of metrics for subsystem > standalone.xml > {code} > curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | wc -l > 109 > curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c > 7 batch > 1 datasources > 7 ejb3 > 6 io > 8 jca > 1 request > 11 transactions > 12 undertow > {code} > standalone-full-ha.xml > {code} > curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | wc -l > 497 > curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c > 7 batch > 1 datasources > 7 ejb3 > 6 io > 8 jca > 354 jgroups > 10 messaging > 1 request > 11 transactions > 18 undertow > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3236) Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3236?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3236: ----------------------------------- Forum Reference: https://stackoverflow.com/a/52984814/893991 > Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter" > ------------------------------------------------------------------------------------------- > > Key: DROOLS-3236 > URL: https://issues.jboss.org/browse/DROOLS-3236 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 7.10.0.Final, 7.11.0.Final, 7.12.0.Final, 7.13.0.Final > Environment: Eclipse photon, Eclipse 2018 09, no special plugin > m2eclipse configured to do-not-manage/ignore any unknown plugin goal (easiest choice) > Reporter: Matteo Mortari > Assignee: Mario Fusco > Priority: Major > Attachments: image-2018-11-05-10-28-50-255.png > > > Since 7.10.0.Final the following error occurs when opening a KJAR project in Eclipse: > !image-2018-11-05-10-28-50-255.png! > Errors occurred during the build. > Errors running builder 'Maven Project Builder' on project '...'. > Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals must be specificed, but found: groupId = 'org.kie' > artifactId = 'kie-maven-plugin' > versionRange = '7.10.0.Final' > goals = '[]' > Please notice kie-maven-plugin 7.9.0.Final and earlier do NOT exhibit this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-133) wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFWIP-133?page=com.atlassian.jira.plugin.... ] Michal Jurc commented on WFWIP-133: ----------------------------------- I would prefer the documentation in XSDs aswell. There's zero maintenance cost as long as the model does not change (and it shouldn't between minor releases), and the payoff was already mentioned by [~rsvoboda]. > wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes > ------------------------------------------------------------------------------------------------------ > > Key: WFWIP-133 > URL: https://issues.jboss.org/browse/WFWIP-133 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes > CLI provides description for attributes via {{/subsystem=microprofile-metrics-smallrye:read-resource-description}}. > Same information should be present in wildfly-microprofile-metrics-smallrye_1_0.xsd via {{<xs:annotation>}} and {{<xs:documentation>}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-133) wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFWIP-133?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFWIP-133: ----------------------------------------- > maintenance cost associated to it I don't expect that message to change > wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes > ------------------------------------------------------------------------------------------------------ > > Key: WFWIP-133 > URL: https://issues.jboss.org/browse/WFWIP-133 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes > CLI provides description for attributes via {{/subsystem=microprofile-metrics-smallrye:read-resource-description}}. > Same information should be present in wildfly-microprofile-metrics-smallrye_1_0.xsd via {{<xs:annotation>}} and {{<xs:documentation>}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-133) wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFWIP-133?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFWIP-133: ----------------------------------------- For example during EAP certification exam there is no access to online resources. There is only EAP documentation and documenattion in xsd. Majority of xsd files have documentation included. These are the reasons why I filed this issue. > wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes > ------------------------------------------------------------------------------------------------------ > > Key: WFWIP-133 > URL: https://issues.jboss.org/browse/WFWIP-133 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes > CLI provides description for attributes via {{/subsystem=microprofile-metrics-smallrye:read-resource-description}}. > Same information should be present in wildfly-microprofile-metrics-smallrye_1_0.xsd via {{<xs:annotation>}} and {{<xs:documentation>}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-127) Subsystem jgroups exposes 354 metrics, no way to expose subset of metrics

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-127?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-127: ----------------------------------- I have addressed this issue by specifying a "exposed-subsystems" in the subsystem management model to define a whitelist of subsystems that will expose their metrics from the MP Metrics HTTP endpoints. I also added support for the "*" wildcard (as a simple way to include metrics from any subsystem). [~rsvoboda] does that address this issue? > Subsystem jgroups exposes 354 metrics, no way to expose subset of metrics > ------------------------------------------------------------------------- > > Key: WFWIP-127 > URL: https://issues.jboss.org/browse/WFWIP-127 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > Subsystem jgroups exposes 354 metrics > There is no way to expose subset of metrics for subsystem > standalone.xml > {code} > curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | wc -l > 109 > curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c > 7 batch > 1 datasources > 7 ejb3 > 6 io > 8 jca > 1 request > 11 transactions > 12 undertow > {code} > standalone-full-ha.xml > {code} > curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | wc -l > 497 > curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c > 7 batch > 1 datasources > 7 ejb3 > 6 io > 8 jca > 354 jgroups > 10 messaging > 1 request > 11 transactions > 18 undertow > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7345) Fix big jboss-beans.xml files truncation

by Jiri Ondrusek (Jira)

[ https://issues.jboss.org/browse/WFLY-7345?page=com.atlassian.jira.plugin.... ] Jiri Ondrusek reassigned WFLY-7345: ----------------------------------- Assignee: Jiri Ondrusek (was: Ales Justin) > Fix big jboss-beans.xml files truncation > ---------------------------------------- > > Key: WFLY-7345 > URL: https://issues.jboss.org/browse/WFLY-7345 > Project: WildFly > Issue Type: Bug > Components: POJO > Affects Versions: 10.1.0.Final > Reporter: Leonardo Penczek > Assignee: Jiri Ondrusek > Priority: Major > Attachments: Test.java, TestMBean.java, test-jboss-beans.xml > > > If the jboss-beans.xml file is big enough, the value of a property.may be truncated, > Fix for this problem: > In the org.jboss.as.pojo.KernelDeploymentParsingProcessor constructor, add this line of code: > inputFactory.setProperty("javax.xml.stream.isCoalescing", Boolean.valueOf(true)); > It prevents the truncation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3244) [DMN Designer] Reuse Workbench Data Objects as DMN Data Types

by Guilherme Carreiro (Jira)

Guilherme Carreiro created DROOLS-3244: ------------------------------------------ Summary: [DMN Designer] Reuse Workbench Data Objects as DMN Data Types Key: DROOLS-3244 URL: https://issues.jboss.org/browse/DROOLS-3244 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Carreiro Assignee: Guilherme Carreiro -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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 November 2018