Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

quarkus-micrometer-registry-jmx is not compatible with Quarkus >= 3.19.0 #6984

Open
jamesnetherton opened this issue Feb 7, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@jamesnetherton
Copy link
Contributor

Bug description

The quarkus-micrometer-registry project needs to adapt to Quarkus migrating the Micrometer extension to @ConfigMapping. Otherwise we get the following on startup:

java.lang.RuntimeException: java.lang.IncompatibleClassChangeError: Found interface io.quarkus.micrometer.runtime.config.MicrometerConfig, but class was expected
	at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:611)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:706)
	at java.base/java.util.Optional.orElseGet(Optional.java:364)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Caused by: java.lang.IncompatibleClassChangeError: Found interface io.quarkus.micrometer.runtime.config.MicrometerConfig, but class was expected
	at io.quarkiverse.micrometer.registry.jmx.deployment.JmxRegistryProcessor$JmxEnabled.getAsBoolean(JmxRegistryProcessor.java:38)
	at io.quarkus.deployment.ExtensionLoader.lambda$and$82(ExtensionLoader.java:940)
	at io.quarkus.deployment.ExtensionLoader.lambda$and$82(ExtensionLoader.java:940)
	at io.quarkus.builder.BuildStepBuilder.buildIf(BuildStepBuilder.java:208)
	at io.quarkus.deployment.ExtensionLoader.lambda$loadStepsFromClass$80(ExtensionLoader.java:780)
	at java.base/java.util.function.Consumer.lambda$andThen$0(Consumer.java:65)
	at io.quarkus.deployment.ExtensionLoader.lambda$loadStepsFromClass$81(ExtensionLoader.java:885)
	at java.base/java.util.function.Consumer.lambda$andThen$0(Consumer.java:65)
	at java.base/java.util.function.Consumer.lambda$andThen$0(Consumer.java:65)
	at java.base/java.util.function.Consumer.lambda$andThen$0(Consumer.java:65)
	at io.quarkus.deployment.QuarkusAugmentor.run(QuarkusAugmentor.java:111)
	at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment(AugmentActionImpl.java:350)
	at io.quarkus.runner.bootstrap.AugmentActionImpl.createInitialRuntimeApplication(AugmentActionImpl.java:271)
	at io.quarkus.runner.bootstrap.AugmentActionImpl.createInitialRuntimeApplication(AugmentActionImpl.java:61)
	at io.quarkus.test.junit.QuarkusTestExtension.doJavaStart(QuarkusTestExtension.java:195)
	at io.quarkus.test.junit.QuarkusTestExtension.ensureStarted(QuarkusTestExtension.java:578)
	at io.quarkus.test.junit.QuarkusTestExtension.beforeAll(QuarkusTestExtension.java:628)
	... 1 more
@jamesnetherton jamesnetherton added the bug Something isn't working label Feb 7, 2025
@jamesnetherton
Copy link
Contributor Author

Seems Guillaume is already on the case with this quarkiverse/quarkus-micrometer-registry#451.

So we can just bump to the new quarkus-micrometer-registry after it is released.

jamesnetherton added a commit to jamesnetherton/camel-quarkus that referenced this issue Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant