More likely refine them to exclude geronimo metrics common. Think it was fixed on master though, not sure it got released.
Le lun. 29 juil. 2019 à 18:07, Ivan Junckes Filho <[email protected]> a écrit : > These are the configs: > openejb.scan.webapp.container = true > openejb.scan.webapp.container.includes = > .*(geronimo|mp-jwt|mp-common|failsafe).* > openejb.scan.webapp.container.excludes = > > Should I remove all of them from the system.properties? Because local I > don't have it. > > On Mon, Jul 29, 2019 at 1:02 PM Romain Manni-Bucau <[email protected]> > wrote: > >> Hi Ivan >> >> Looks like a tomee config issue, common module shouldnt be scanned, can >> you check your exclusion list? >> >> Le lun. 29 juil. 2019 à 17:47, Ivan Junckes Filho <[email protected]> >> a écrit : >> >>> Hey guys, there is an interesting issue happening with metrics in tomee. >>> >>> When I can /metrics in the tomee runnning in my localhost wihout docker >>> I am able to access /metrics endpoint. But in the environment that I use >>> docker to run TomEE I get the issue below on calling /metrics. >>> >>> Anybody can help? >>> >>> 29-Jul-2019 12:41:56.870 WARNING [https-jsse-nio-8181-exec-7] >>> org.apache.cxf.jaxrs.model.OperationResourceInfoComparator.compare Both >>> org.apache.geronimo.microprofile.metrics.jaxrs.CdiMetricsEndpoints#getText >>> and >>> org.apache.geronimo.microprofile.metrics.common.jaxrs.MetricsEndpoints#getText >>> are equal candidates for handling the current request which can lead to >>> unpredictable results >>> >>
