January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-12854) Consider to allow non-resuable metrics of the same name in subdeployments

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12854?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-12854: ---------------------------------- Assignee: Jason Lee (was: Jeff Mesnil) > Consider to allow non-resuable metrics of the same name in subdeployments > ------------------------------------------------------------------------- > > Key: WFLY-12854 > URL: https://issues.redhat.com/browse/WFLY-12854 > Project: WildFly > Issue Type: Feature Request > Components: MP Metrics > Reporter: Ivan Straka > Assignee: Jason Lee > Priority: Major > > If two method annotated to use MP Metrics have same name. In case of _Counters_ (example): > * They are reusable there is actually one MP metric and both method invocation are counted to a single metric. > * They are non-reusable: > ** They are in the same deployment - ERROR is logged and metrics are not registerd > ** They are in different deployments > *** (X) MP Config _mp.metrics.appName_ is used thus metrics are registered under _configured_name;_app=the value_ thus they are registered under different name > *** MP Config _mp.metrics.appName_ is not used - ERROR is logged and metrics are not registerd > Now I'd like to talk about the (X) option. This is valid for two scenarios: > * Multiple deployments > * Deployment with sub-deployments. > In Multiple deployments I am able to to annotate two methods with non-reusable metric of the same name. I need to set MP Config _mp.metrics.appName_ property. Then I can select the metric using a tag. > However per https://github.com/smallrye/smallrye-metrics/issues/216 I am not able to do that in deployment with sub-deployments scenario. > This is inconsistent behavior and it would be good to have it implemented. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-12690) Metrics call causes java.util.ConcurrentModificationException

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12690?page=com.atlassian.jira.plugi... ] Jeff Mesnil resolved WFLY-12690. -------------------------------- Fix Version/s: 19.0.0.Beta3 Resolution: Done > Metrics call causes java.util.ConcurrentModificationException > ------------------------------------------------------------- > > Key: WFLY-12690 > URL: https://issues.redhat.com/browse/WFLY-12690 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Affects Versions: 18.0.0.Final > Environment: I ran the tests in our integration test environment. This includes a prometheus, scraping the metrics with an intervall of 5s. > Reporter: Ralf Battenfeld > Assignee: Jeff Mesnil > Priority: Major > Fix For: 19.0.0.Beta3 > > > Hi I ran our integrations tests together with prometheus calls. In Wildfly 18, I get this errors constantly: > {code:java} > 2019-10-18 14:22:57,284 ERROR [io.undertow.request] (management I/O-2) UT005071: Undertow request failed HttpServerExchange{ GET /metrics}: java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextNode(HashMap.java:1445) > at java.util.HashMap$EntryIterator.next(HashMap.java:1479) > at java.util.HashMap$EntryIterator.next(HashMap.java:1477) > at java.util.HashMap.putMapEntries(HashMap.java:512) > at java.util.HashMap.<init>(HashMap.java:490) > at io.smallrye.metrics.MetricsRegistryImpl.getMetadata(MetricsRegistryImpl.java:560) > at io.smallrye.metrics.exporters.OpenMetricsExporter.exposeEntries(OpenMetricsExporter.java:157) > at io.smallrye.metrics.exporters.OpenMetricsExporter.getEntriesForScope(OpenMetricsExporter.java:150) > at io.smallrye.metrics.exporters.OpenMetricsExporter.exportAllScopes(OpenMetricsExporter.java:101) > at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:116) > at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:73) > at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:81) > at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51) > at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35) > at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91) > at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211) > at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92) > at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78) > at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49) > at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57) > at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75) > at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:666) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376) > at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255) > at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136) > at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:59) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:591) > {code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1263) Fix openshift_api.service_details ports part not to ignore information

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1263?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1263: ---------------------------------- Sprint: Kiali Sprint #51 > Fix openshift_api.service_details ports part not to ignore information > ---------------------------------------------------------------------- > > Key: SWSQE-1263 > URL: https://issues.redhat.com/browse/SWSQE-1263 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Happens on dedicated clusters, port name is ignore while reading. > Fix also on kiali-2.0 branch. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1183) OC API - Application list - Add health

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1183?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1183. ----------------------------------- Resolution: Done > OC API - Application list - Add health > -------------------------------------- > > Key: SWSQE-1183 > URL: https://issues.redhat.com/browse/SWSQE-1183 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > openshift_api.application_list > application_details > TODO: health needs to be added -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1184) OC API - Workload list - Add health

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1184?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1184. ----------------------------------- Resolution: Done > OC API - Workload list - Add health > ----------------------------------- > > Key: SWSQE-1184 > URL: https://issues.redhat.com/browse/SWSQE-1184 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > openshift_api.workload_list > workload_details > TODO: heath needs to be added -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5953) Generalize accumulate function and improve optaplanner compatibility

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5953?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5953: -------------------------------- Issue Type: Enhancement (was: Bug) > Generalize accumulate function and improve optaplanner compatibility > -------------------------------------------------------------------- > > Key: DROOLS-5953 > URL: https://issues.redhat.com/browse/DROOLS-5953 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5247) IllegalArgumentException and CLI crash with read-attribute in /system-property

by David Le Borgne (Jira)

[ https://issues.redhat.com/browse/WFCORE-5247?page=com.atlassian.jira.plug... ] David Le Borgne updated WFCORE-5247: ------------------------------------ Description: Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. {{/opt/wildfly/bin/jboss-cli.sh --connect}} {{[standalone@localhost:9990 /] cd /system-property}} {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} {{Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} was: Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. {{/opt/wildfly/bin/jboss-cli.sh --connect}} {{[standalone@localhost:9990 /] cd /system-property}} {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} {{ Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} > IllegalArgumentException and CLI crash with read-attribute in /system-property > ------------------------------------------------------------------------------ > > Key: WFCORE-5247 > URL: https://issues.redhat.com/browse/WFCORE-5247 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: David Le Borgne > Assignee: Jean Francois Denise > Priority: Major > Attachments: stack_trace.txt > > > Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. > > {{/opt/wildfly/bin/jboss-cli.sh --connect}} > {{[standalone@localhost:9990 /] cd /system-property}} > {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} > {{Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5247) IllegalArgumentException and CLI crash with read-attribute in /system-property

by David Le Borgne (Jira)

David Le Borgne created WFCORE-5247: --------------------------------------- Summary: IllegalArgumentException and CLI crash with read-attribute in /system-property Key: WFCORE-5247 URL: https://issues.redhat.com/browse/WFCORE-5247 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 14.0.0.Final Reporter: David Le Borgne Assignee: Jean Francois Denise Attachments: stack_trace.txt Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. {{/opt/wildfly/bin/jboss-cli.sh --connect}} {{[standalone@localhost:9990 /] cd /system-property}} {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} {{ Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2525) Replace XML parse for configuration with simple parser

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2525?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2525. ---------------------------- Resolution: Done > Replace XML parse for configuration with simple parser > ------------------------------------------------------ > > Key: JGRP-2525 > URL: https://issues.redhat.com/browse/JGRP-2525 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.11, 5.1.3 > > > Similarly to JGRP-2524, this replaces the javax.xml classes used for parsing of configuration with a simple parser. > This reduces the number of classes pulled in and should result in a smaller memory footprint. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2525) Replace XML parse for configuration with simple parser

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2525?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2525: --------------------------- Fix Version/s: 4.2.11 (was: 4.2.12) > Replace XML parse for configuration with simple parser > ------------------------------------------------------ > > Key: JGRP-2525 > URL: https://issues.redhat.com/browse/JGRP-2525 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.11, 5.1.3 > > > Similarly to JGRP-2524, this replaces the javax.xml classes used for parsing of configuration with a simple parser. > This reduces the number of classes pulled in and should result in a smaller memory footprint. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 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 January 2021