November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3351) [DMN Designer] Font size information is not being persisted

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3351?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3351: ----------------------------------- Story Points: 2 > [DMN Designer] Font size information is not being persisted > ----------------------------------------------------------- > > Key: DROOLS-3351 > URL: https://issues.jboss.org/browse/DROOLS-3351 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Matteo Mortari > Priority: Minor > Labels: drools-tools > Attachments: error.gif > > > When the user configures a bigger font size, the information is not persisted. > Steps to reproduce: > !error.gif|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

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

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFWIP-127?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFWIP-127: ------------------------------------ [~jmesnil] Does this imply that my suggestion above is not necessary? > Subsystem jgroups exposes 180 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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-131) SmallRye Metrics - MetricsRegistryImpl - removal of entry from map which is currently iterated

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-131?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-131: ----------------------------------- Reported upstream at https://github.com/smallrye/smallrye-metrics/issues/36 > SmallRye Metrics - MetricsRegistryImpl - removal of entry from map which is currently iterated > ---------------------------------------------------------------------------------------------- > > Key: WFWIP-131 > URL: https://issues.jboss.org/browse/WFWIP-131 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > SmallRye Metrics - MetricsRegistryImpl - removal of entry from map which is currently iterated > https://github.com/smallrye/smallrye-metrics/blob/master/implementation/s... > Method {{removeMatching}} is iterating over {{metricMap}}. If there is a match {{remove}} method is called. This method removes entry from {{metricMap}} and from {{metadataMap}}. > I don't like the fact that the entry is removed from the map by external method while the map is currently iterated by the {{removeMatching}} method. > I think https://docs.oracle.com/javase/8/docs/api/java/util/Iterator.html#remove-- should be called in {{removeMatching}} for {{metricMap}} entry + invocation of metadataMap.remove(entry.getKey()) + log mesasge; -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-130) SmallRye Metrics - JmxWorker - findKeyForValueToBeReplaced could use some polish

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-130?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-130: ----------------------------------- Reported upstream at https://github.com/smallrye/smallrye-metrics/issues/35 > SmallRye Metrics - JmxWorker - findKeyForValueToBeReplaced could use some polish > -------------------------------------------------------------------------------- > > Key: WFWIP-130 > URL: https://issues.jboss.org/browse/WFWIP-130 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > SmallRye Metrics - JmxWorker - findKeyForValueToBeReplaced could use some polish > https://github.com/smallrye/smallrye-metrics/blob/master/implementation/s... > - iterate entrySet instead of keySet > - can it happen that there are more entries with value '*' ? > - shouldn't the for cycle end when the (first?) match is found ? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-127) Subsystem jgroups exposes 180 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 resolved WFWIP-127. ------------------------------- Resolution: Won't Do JGroups exposes a lot of metrics but that should be manageable when metrics are properly named and use labels (we should go from 180 metrics to a dozen or so) > Subsystem jgroups exposes 180 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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11420) Configure statistics-enabled for subsystems that exposes metrics

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11420?page=com.atlassian.jira.plugin... ] Jeff Mesnil moved WFWIP-141 to WFLY-11420: ------------------------------------------ Project: WildFly (was: WildFly WIP) Key: WFLY-11420 (was: WFWIP-141) Issue Type: Enhancement (was: Bug) Component/s: MP Metrics (was: MP Metrics) > Configure statistics-enabled for subsystems that exposes metrics > ---------------------------------------------------------------- > > Key: WFLY-11420 > URL: https://issues.jboss.org/browse/WFLY-11420 > Project: WildFly > Issue Type: Enhancement > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > Vendor metrics - subsystem - statistics-enabled to get valid data > I was playing with vendor metrics and I received a lot of zeros. > {code} > curl http://localhost:10090/metrics/vendor 2>/dev/null | grep -v TYPE | grep -v HELP | sort > {code} > Note: I use {{-Djboss.socket.binding.port-offset=100}} > So I started to wonder why and it's because of statistics are not enabled. > When I enabled statistics for Undertow and hit the WF server main page I saw some changes in metrics. > {code} > subsystem=undertow/:write-attribute(name=statistics-enabled, value=true) > {code} > Later I realized this scenario is also mentioned in analysis, section WildFly Metrics with undefined value / statistic-enabled = false > https://github.com/wildfly/wildfly-proposals/blob/cc189b56720951875aa9610... > So this is mainly tracking + discussion point now. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-141) Vendor metrics - subsystem - statistics-enabled to get valid data

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-141?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-141: ----------------------------------- The metrics subsystem ignores WildFly metrics that have undefined value (e.g. if their statistics-enabled that controls them is false) This ensures that the subsystem only reports actual metric value (otherwise we have to open bugs to fix it). Standalone configs could be further enhanced by using a global env var to enable the statistics from the subsystems that reports such metrics (undertow, messaging-activemq, etc.) > Vendor metrics - subsystem - statistics-enabled to get valid data > ----------------------------------------------------------------- > > Key: WFWIP-141 > URL: https://issues.jboss.org/browse/WFWIP-141 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > Vendor metrics - subsystem - statistics-enabled to get valid data > I was playing with vendor metrics and I received a lot of zeros. > {code} > curl http://localhost:10090/metrics/vendor 2>/dev/null | grep -v TYPE | grep -v HELP | sort > {code} > Note: I use {{-Djboss.socket.binding.port-offset=100}} > So I started to wonder why and it's because of statistics are not enabled. > When I enabled statistics for Undertow and hit the WF server main page I saw some changes in metrics. > {code} > subsystem=undertow/:write-attribute(name=statistics-enabled, value=true) > {code} > Later I realized this scenario is also mentioned in analysis, section WildFly Metrics with undefined value / statistic-enabled = false > https://github.com/wildfly/wildfly-proposals/blob/cc189b56720951875aa9610... > So this is mainly tracking + discussion point now. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-141) Configure statistics-enabled for subsystems that exposes metrics

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-141?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFWIP-141: ------------------------------ Summary: Configure statistics-enabled for subsystems that exposes metrics (was: Vendor metrics - subsystem - statistics-enabled to get valid data) > Configure statistics-enabled for subsystems that exposes metrics > ---------------------------------------------------------------- > > Key: WFWIP-141 > URL: https://issues.jboss.org/browse/WFWIP-141 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > Vendor metrics - subsystem - statistics-enabled to get valid data > I was playing with vendor metrics and I received a lot of zeros. > {code} > curl http://localhost:10090/metrics/vendor 2>/dev/null | grep -v TYPE | grep -v HELP | sort > {code} > Note: I use {{-Djboss.socket.binding.port-offset=100}} > So I started to wonder why and it's because of statistics are not enabled. > When I enabled statistics for Undertow and hit the WF server main page I saw some changes in metrics. > {code} > subsystem=undertow/:write-attribute(name=statistics-enabled, value=true) > {code} > Later I realized this scenario is also mentioned in analysis, section WildFly Metrics with undefined value / statistic-enabled = false > https://github.com/wildfly/wildfly-proposals/blob/cc189b56720951875aa9610... > So this is mainly tracking + discussion point now. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3355) Discuss and verify Assembler/Weaver API to better support for jBPM and generic runtimes

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3355?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3355: ----------------------------------- Story Points: 5 > Discuss and verify Assembler/Weaver API to better support for jBPM and generic runtimes > --------------------------------------------------------------------------------------- > > Key: DROOLS-3355 > URL: https://issues.jboss.org/browse/DROOLS-3355 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Current API may be too Drools/Rule-Engine-centric, might want to rethink it -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3355) Discuss and verify Assembler/Weaver API to better support for jBPM and generic runtimes

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3355?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3355: ----------------------------------- Sprint: 2018 Week 48-50 > Discuss and verify Assembler/Weaver API to better support for jBPM and generic runtimes > --------------------------------------------------------------------------------------- > > Key: DROOLS-3355 > URL: https://issues.jboss.org/browse/DROOLS-3355 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Current API may be too Drools/Rule-Engine-centric, might want to rethink it -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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