-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
LogManager error reported during container startup using Keycloak 26.0.1 #164
Comments
Thanks for reporting. The problem is, that actually the dependencies in the using project are responsible for this, as they are pulling the I've not yet a good idea how to solve this and if this is even solvable from this libs side. If you have an idea, it's more than welcome. I think I need some more time to think about it (aside my regular work). |
Yes, and as I pointed out it's easily worked around, so not a high priority issue at all. If nothing else, might be worth a mention in the README. Thanks for the quick response! |
Yes, the workaround is easy, but has to be done in the using project. |
I was able to fix this warning by adding the <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
<version>3.5.0</version>
<executions>
<execution>
<id>integration-tests</id>
<goals>
<goal>integration-test</goal>
<goal>verify</goal>
</goals>
</execution>
</executions>
<configuration>
<argLine>-Djava.util.logging.manager=org.jboss.logmanager.LogManager</argLine>
</configuration>
</plugin> |
Describe the bug
Just tried moving my environment to Keycloak 26.0.1. Running my integration tests which starts a Keycloak testcontainer I see an ERROR during startup (see logging output). Also note that this error appears to be benign (the testcontainer starts successfully) except that I had to exclude slf4j-jboss-logmanager to see log output from the testcontainer.
This allows my reload4j dependency to work:
Version
3.4.0
Expected behavior
The testcontainer should start without the ERROR message.
Actual behavior
No response
How to Reproduce?
No response
Relevant log output
Anything else?
No response
The text was updated successfully, but these errors were encountered: