vladmihalcea
commented
6 years ago You can have both flexy-pool:flexy-codahale-metrics and flexy-dropwizard-metrics jars in your project. Or you can exclude the flexy-codahale-metrics one.
The problem is that, on your classpath, you have the old Dorpwizard 3 library:
com/codahale/metrics/JmxReporter
And FlexyPool finds it at runtime and assumes that's what you want to use. Add a breakpoint in MetricsFactoryResolver class inside the resolve method and check what it finds.
Additionally, add a hard dependency on DW 4:
<dependency>
<groupId>io.dropwizard.metrics</groupId>
<artifactId>metrics-core</artifactId>
<version>4.0.2</version>
</dependency>The reason why there are two artifacts is that FlexyPool works with both DW3 and DW4. For more details, check out this article.
johnament
While starting to integrate flexy-pool with a Java SE app, I found the following CNFE:
This was confusing, since I didn't declare any metrics runtime (yet), and was planning to use DWM4.
The following is part of the dependency tree I see within my app:
I wouldn't expect a hard compile time dependency on these components, they don't seem like they're hard dependencies either within the code. So should they be removed? Or excluded?