January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-13779) MicroProfile Metrics tests started to fail since changes in ConfigSource

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13779?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-13779: ---------------------------------- Assignee: Jason Lee (was: Jeff Mesnil) > MicroProfile Metrics tests started to fail since changes in ConfigSource > ------------------------------------------------------------------------ > > Key: WFLY-13779 > URL: https://issues.redhat.com/browse/WFLY-13779 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Sultan Zhantemirov > Assignee: Jason Lee > Priority: Major > > WildFly build: 21.0.0.Beta1-SNAPSHOT > Java: oracle-java-11 > A several failures appeared in our small standalone test suite [1] for MicroProfile on WF/EAP. To be more specific, a few failures in MP Metrics that have one common cause: > {noformat} > java.lang.RuntimeException: config.source.properties.path property not defined > {noformat} > caused by line [2]. > I have a reason to believe that this PR [3] could be reason of these failures. What should be done in this case? > Thank you. > [1] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite/tree/master/m... > [2] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite/blob/8b726042... > [3] - https://github.com/wildfly/wildfly/pull/13247 > -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14038) Intermittent failure MeterTest.testRates org.eclipse.microprofile.metrics.tck.metrics

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14038?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-14038: ---------------------------------- Assignee: Jason Lee (was: Jeff Mesnil) > Intermittent failure MeterTest.testRates org.eclipse.microprofile.metrics.tck.metrics > ------------------------------------------------------------------------------------- > > Key: WFLY-14038 > URL: https://issues.redhat.com/browse/WFLY-14038 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Cheng Fang > Assignee: Jason Lee > Priority: Major > > In WildFly CI, the test {{MeterTest.testRates org.eclipse.microprofile.metrics.tck.metrics}} failed intermittently. > For exmaple, in [this Windows JDK 11 test run|https://ci.wildfly.org/buildConfiguration/WF_PullRequest_WindowsJdk11...]. > {code} > java.lang.AssertionError: expected:<100.0> but was:<112.03899899654196> > at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.junit.Assert.fail(Assert.java:89) > at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.junit.Assert.failNotEquals(Assert.java:835) > at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.junit.Assert.assertEquals(Assert.java:555) > at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.junit.Assert.assertEquals(Assert.java:685) > at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.eclipse.microprofile.metrics.tck.util.TestUtils.assertEqualsWithTolerance(TestUtils.java:41) > at deployment.ec140433-2b01-4b7c-95ad-9c5f30dc8baa.war//org.eclipse.microprofile.metrics.tck.metrics.MeterTest.testRates(MeterTest.java:96) > {code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

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

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-11933?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-11933: ---------------------------------- Assignee: Jason Lee (was: Jeff Mesnil) > Error when accessing metrics with RBAC enabled > ---------------------------------------------- > > Key: WFLY-11933 > URL: https://issues.redhat.com/browse/WFLY-11933 > Project: WildFly > Issue Type: Bug > Components: Management, MP Metrics > Affects Versions: 16.0.0.Final, 17.0.0.Final, 17.0.1.Final, 21.0.0.Final > Reporter: Claudio Weiler > Assignee: Jason Lee > Priority: Major > > Accordingly to https://docs.wildfly.org/17/Admin_Guide.html#http-endpoint-2 and https://wildscribe.github.io/WildFly/17.0/subsystem/microprofile-metrics-..., access to metrics endpoint is controlled by the security-enabled attribute. > When this attribute is set to false, there is an Exception when metrics are accessed. By default, this attribute is set to false on standalone.xml config. > Please, refer to steps to reproduce. This error occurs only when RBAC are enabled. > When RBAC is enabled for management in Wildfly, 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 (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-11731) IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-11731?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-11731: ---------------------------------- Assignee: Jason Lee (was: Jeff Mesnil) > IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists > ------------------------------------------------------------------------------------------------ > > Key: WFLY-11731 > URL: https://issues.redhat.com/browse/WFLY-11731 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Brian Stansberry > Assignee: Jason Lee > Priority: Major > > CI failure due to $subject -- ConstantRoleMapperTestCase in https://ci.wildfly.org/viewLog.html?buildId=139312&buildTypeId=WFPR&tab=b... > {code} > &amp#27;[0m&amp#27;[31m11:45:07,066 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildlfy.extension.microprofile.metrics.wildfly-registrar: org.jboss.msc.service.StartException in service org.wildlfy.extension.microprofile.metrics.wildfly-registrar: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalArgumentException: A metric with name classloader.currentLoadedClass.count already exists > at io.smallrye.metrics.MetricsRegistryImpl.register(MetricsRegistryImpl.java:113) > at io.smallrye.metrics.setup.JmxRegistrar.register(JmxRegistrar.java:54) > at io.smallrye.metrics.setup.JmxRegistrar.register(JmxRegistrar.java:38) > at io.smallrye.metrics.setup.JmxRegistrar.init(JmxRegistrar.java:30) > at org.wildfly.extension.microprofile.metrics.MetricsRegistrationService.start(MetricsRegistrationService.java:91) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) > ... 6 more > {code} > I have a feeling this has already been reported but simple searching didn't find it. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-11638) MP Metrics - sort alphabetically /metrics output

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-11638?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFLY-11638: ---------------------------------- Assignee: Jason Lee (was: Jeff Mesnil) > MP Metrics - sort alphabetically /metrics output > ------------------------------------------------ > > Key: WFLY-11638 > URL: https://issues.redhat.com/browse/WFLY-11638 > Project: WildFly > Issue Type: Enhancement > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Jason Lee > Priority: Major > > MP Metrics - sort alphabetically /metrics output > When playing with https://github.com/wildfly/wildfly/pull/11949 I got upset about metrics not being sorted alphabetically or at least grouped together. > My use case was to look at wildfly_undertow_** metrics via browser. > base: and vendor: metrics are grouped together, WF subsystem metrics not - e.g. wildfly_undertow_** metrics were listed on 4 different places. > If alphabetical order is not easy to be achieved, subsystem metrics should be at least grouped together. > I know machines do not care about the order, but people have to look at /metrics too (from time to time ...). -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 9 months

1
0
0 / 0

[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)

3 years, 9 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)

3 years, 9 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)

3 years, 9 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)

3 years, 9 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)

3 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021