November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4115) JDK11 - GC logging format needs to be reviewed

by Aaron Ogburn (Jira)

[ https://issues.jboss.org/browse/WFCORE-4115?page=com.atlassian.jira.plugi... ] Aaron Ogburn commented on WFCORE-4115: -------------------------------------- [~mkopecky], any sample of GC logs you're comparing in verbosity? > JDK11 - GC logging format needs to be reviewed > ---------------------------------------------- > > Key: WFCORE-4115 > URL: https://issues.jboss.org/browse/WFCORE-4115 > Project: WildFly Core > Issue Type: Bug > Components: Scripts, Server > Reporter: Marek Kopecký > Assignee: James Perkins > Priority: Major > Labels: Java11, jdk11 > > * Weird naming of gc log files > ** I test this with JDK11 > ** I start standalone and stop standalone > ** JDK10 creates JBOSS_HOME/standalone/log/gc.log (with detailed information) and JBOSS_HOME/standalone/log/gc.log.0 (with brief summary of gc logging) > ** I start standalone and stop standalone again > ** JDK10 moves original gc.log to gc.log.1 > ** JDK10 keep original gc.log.0 > ** JDK10 creates new gc.log (with detailed information) and gc.log.2 (with brief summary of gc logging) > ** Can this be changed by GC settings? > * GC logs are much more verbose against jdk8 gc logs. Can this be fixed by some JDK10 gc settings? > This is follow up for WFCORE-3996 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3031) [DMN Designer] UX for Expand / Collapse all

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3031?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3031: -------------------------------- Sprint: (was: 2018 Week 45-47) > [DMN Designer] UX for Expand / Collapse all > ------------------------------------------- > > Key: DROOLS-3031 > URL: https://issues.jboss.org/browse/DROOLS-3031 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog. > h2. Manual acceptance test > - Expand > -- All collapsed initially > -- Something collapsed initially, something expanded already > -- All expanded already > - Collapse > -- All expanded initially > -- Something expanded initially, something collapsed already > -- All collapsed already > - No error warning in browser console log -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) Design data type constraints UX

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Sprint: 2018 Week 33-35 (was: 2018 Week 33-35, 2018 Week 45-47) > Design data type constraints UX > -------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-136) OpenLiberty providse base:cpu_process_cpu_load_percent, WF doesn't

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-136?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-136: ----------------------------------- fixed in dev branch: {code} $ curl http://localhost:9990/metrics/base/ | grep cpu_process # HELP base:cpu_process_cpu_load Displays the "recent cpu usage" for the Java Virtual Machine process. # TYPE base:cpu_process_cpu_load gauge base:cpu_process_cpu_load 4.282571006977806E-4 {code} > OpenLiberty providse base:cpu_process_cpu_load_percent, WF doesn't > ------------------------------------------------------------------ > > Key: WFWIP-136 > URL: https://issues.jboss.org/browse/WFWIP-136 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > OpenLiberty providse base:cpu_process_cpu_load_percent, WF doesn't > Example: > {code} > base:cpu_process_cpu_load_percent 0.001126147378413068 > {code} > Using setup described here: https://github.com/rsvoboda/rsvoboda-playground/tree/master/Prometheus#op... > {code} > curl https://localhost:9443/metrics/base --insecure -v -u theUser:thePassword 2>/dev/null | grep -v TYPE | grep -v HELP | sort > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-136) OpenLiberty providse base:cpu_process_cpu_load_percent, WF doesn't

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-136?page=com.atlassian.jira.plugin.... ] Jeff Mesnil resolved WFWIP-136. ------------------------------- Resolution: Done > OpenLiberty providse base:cpu_process_cpu_load_percent, WF doesn't > ------------------------------------------------------------------ > > Key: WFWIP-136 > URL: https://issues.jboss.org/browse/WFWIP-136 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > OpenLiberty providse base:cpu_process_cpu_load_percent, WF doesn't > Example: > {code} > base:cpu_process_cpu_load_percent 0.001126147378413068 > {code} > Using setup described here: https://github.com/rsvoboda/rsvoboda-playground/tree/master/Prometheus#op... > {code} > curl https://localhost:9443/metrics/base --insecure -v -u theUser:thePassword 2>/dev/null | grep -v TYPE | grep -v HELP | sort > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-137) Integers are printed as floats with trailing .0

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-137?page=com.atlassian.jira.plugin.... ] Jeff Mesnil resolved WFWIP-137. ------------------------------- Resolution: Done > Integers are printed as floats with trailing .0 > ----------------------------------------------- > > Key: WFWIP-137 > URL: https://issues.jboss.org/browse/WFWIP-137 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > Integers are printed as floats with trailing .0 > {code} > base:classloader_current_loaded_class_count 11135.0 > base:classloader_total_loaded_class_count 11171.0 > base:classloader_total_unloaded_class_count 36.0 > base:cpu_available_processors 8.0 > base:gc_g1_old_generation_count 0.0 > base:gc_g1_old_generation_time_seconds 0.0 > base:gc_g1_young_generation_count 20.0 > base:thread_count 50.0 > base:thread_daemon_count 11.0 > base:thread_max_count 121.0 > {code} > Payara, OpenLiberty and Helidon report integers as integers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-137) Integers are printed as floats with trailing .0

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-137?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-137: ----------------------------------- I am using a Gauge to represent all metrics from WildFly subsystems. At first, I was getting the value as a Double in all cases. I have refined that to distinguish between INT, LONG and other numeric ModelType in the dev branch (35ceb2ed6ac29a6e65e2a89e53b4e99988c37593) > Integers are printed as floats with trailing .0 > ----------------------------------------------- > > Key: WFWIP-137 > URL: https://issues.jboss.org/browse/WFWIP-137 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Major > > Integers are printed as floats with trailing .0 > {code} > base:classloader_current_loaded_class_count 11135.0 > base:classloader_total_loaded_class_count 11171.0 > base:classloader_total_unloaded_class_count 36.0 > base:cpu_available_processors 8.0 > base:gc_g1_old_generation_count 0.0 > base:gc_g1_old_generation_time_seconds 0.0 > base:gc_g1_young_generation_count 20.0 > base:thread_count 50.0 > base:thread_daemon_count 11.0 > base:thread_max_count 121.0 > {code} > Payara, OpenLiberty and Helidon report integers as integers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-138) Float numbers rendered with 'E-' string, at least jvm_uptime_seconds should have different value

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-138?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-138: ----------------------------------- I can confirm that time-related metrics were fixed in https://github.com/smallrye/smallrye-metrics/issues/9 > Float numbers rendered with 'E-' string, at least jvm_uptime_seconds should have different value > ------------------------------------------------------------------------------------------------ > > Key: WFWIP-138 > URL: https://issues.jboss.org/browse/WFWIP-138 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Blocker > > Float numbers rendered with 'E-' string, at least jvm_uptime_seconds should have different value > {code} > base:gc_g1_young_generation_time_seconds 7.7E-8 > base:jvm_uptime_seconds 1.85616E-4 > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-142) Vendor metrics - loaded_modules reports incorrect value

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-142?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-142: ----------------------------------- In the meantime, I have removed the loadedModules metric until it can be correctly measured. > Vendor metrics - loaded_modules reports incorrect value > ------------------------------------------------------- > > Key: WFWIP-142 > URL: https://issues.jboss.org/browse/WFWIP-142 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Blocker > > Vendor metrics - loaded_modules reports incorrect value > {code} > curl http://localhost:10090/metrics/vendor 2>/dev/null | grep loaded_modules > # HELP vendor:loaded_modules Number of loaded modules > # TYPE vendor:loaded_modules gauge > vendor:loaded_modules 23.0 > {code} > When I tried Thorntail 2 based deployment I got {{vendor:loaded_modules 298.0}} > WF probably reports incorrect value for loaded modules. > The same value is reported when I deploy {{quickstart/helloworld-rs/target/helloworld-rs.war}} application. For sure new modules are triggered by deplyment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-142) Vendor metrics - loaded_modules reports incorrect value

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-142?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-142: ----------------------------------- the ObjectName in io/smallrye/metrics/vendor-metrics.properties was wrong. It should be jboss.modules:type=ModuleLoader,name=LocalModuleLoader-3 (and it reports ~300 modules). However, [~dmlloyd] confirmed to me that the ObjectName can change (the increment at the end can be -3 or -4, etc. depending on config and race conditions. We should not rely on JMX to get the number of modules. Instead, we could implement our own gauge that get the number directly from the correct ModuleLoader > Vendor metrics - loaded_modules reports incorrect value > ------------------------------------------------------- > > Key: WFWIP-142 > URL: https://issues.jboss.org/browse/WFWIP-142 > Project: WildFly WIP > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Blocker > > Vendor metrics - loaded_modules reports incorrect value > {code} > curl http://localhost:10090/metrics/vendor 2>/dev/null | grep loaded_modules > # HELP vendor:loaded_modules Number of loaded modules > # TYPE vendor:loaded_modules gauge > vendor:loaded_modules 23.0 > {code} > When I tried Thorntail 2 based deployment I got {{vendor:loaded_modules 298.0}} > WF probably reports incorrect value for loaded modules. > The same value is reported when I deploy {{quickstart/helloworld-rs/target/helloworld-rs.war}} application. For sure new modules are triggered by deplyment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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