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

ClassNotFoundException in SpringHawtioContextListener #2751

Closed
creckord opened this issue Jun 30, 2022 · 0 comments · Fixed by #2758
Closed

ClassNotFoundException in SpringHawtioContextListener #2751

creckord opened this issue Jun 30, 2022 · 0 comments · Fixed by #2758
Milestone

Comments

@creckord
Copy link

After upgrading from HawtIO 2.14.5 to 2.15.0, our applications won't start anymore due to a ClassNotFoundException in SpringHawtioContextListener:

java.lang.ClassNotFoundException: ch.qos.logback.core.Appender
	at jdk.internal.loader.BuiltinClassLoader.loadClass(Unknown Source) ~[?:?]
	at jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Unknown Source) ~[?:?]
	at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:?]
	at io.hawt.springboot.SpringHawtioContextListener.<init>(SpringHawtioContextListener.java:21) ~[hawtio-springboot-2.15.0.jar:2.15.0]	
	at io.hawt.springboot.HawtioManagementConfiguration.hawtioContextListener(HawtioManagementConfiguration.java:279) ~[hawtio-springboot-2.15.0.jar:2.15.0]

This is caused by the following addition in PR 2732:

+               this.logQuery = new LogbackLogQuery();

We are using Log4J2 in our aplications, and Logback is not part of the deployment.

Since SpringHawtioContextListener is part of hawtio-springboot and not of the hawtio-log-logback plugin, I don't think it should have a hard requirement on Logback. And since the bean configuration in HawtioManagementConfiguration is unconditional, it's also hard to override with a different implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants