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

Spring Boot 3.2.0 regressions. #24533

Closed
1 of 3 tasks
mshima opened this issue Dec 11, 2023 · 2 comments
Closed
1 of 3 tasks

Spring Boot 3.2.0 regressions. #24533

mshima opened this issue Dec 11, 2023 · 2 comments

Comments

@mshima
Copy link
Member

mshima commented Dec 11, 2023

Overview of the issue
Motivation for or Use Case
Reproduce the error
  SLF4J: Class path contains multiple SLF4J providers.
  SLF4J: Found provider [org.slf4j.jul.JULServiceProvider@38cccef]
  SLF4J: Found provider [ch.qos.logback.classic.spi.LogbackServiceProvider@5679c6c6]
  SLF4J: See https://www.slf4j.org/codes.html#multiple_bindings for an explanation.
  SLF4J: Actual provider is of type [org.slf4j.jul.JULServiceProvider@38cccef]
  Error: Exception in thread "main" java.lang.IllegalArgumentException: LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation (class org.slf4j.jul.JDK14LoggerFactory loaded from file:/app/libs/slf4j-jdk14-2.0.9.jar). If you are using WebLogic you will need to add 'org.slf4j' to prefer-application-packages in WEB-INF/weblogic.xml: org.slf4j.jul.JDK14LoggerFactory
  	at org.springframework.util.Assert.instanceCheckFailed(Assert.java:592)
  	at org.springframework.util.Assert.isInstanceOf(Assert.java:511)
  	at org.springframework.boot.logging.logback.LogbackLoggingSystem.getLoggerContext(LogbackLoggingSystem.java:396)
  	at org.springframework.boot.logging.logback.LogbackLoggingSystem.beforeInitialize(LogbackLoggingSystem.java:124)
  	at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationStartingEvent(LoggingApplicationListener.java:238)
  	at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:220)
  	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:178)
2023-12-11T05:08:23.890Z  WARN 6132 --- [oundedElastic-3] reactor.core.Exceptions                  : throwIfFatal detected a jvm fatal exception, which is thrown and logged below: 
[0] 
[0] java.lang.NoClassDefFoundError: com/fasterxml/jackson/databind/util/EnumValues
[0] 	at com.fasterxml.jackson.databind.ser.std.EnumSerializer.construct(EnumSerializer.java:101)

Related issues
Suggest a Fix
JHipster Version(s)
JHipster configuration
Entity configuration(s) entityName.json files generated in the .jhipster directory
Browsers and Operating System
  • Checking this box is mandatory (this is just to show you read everything)
@atomfrede
Copy link
Member

I tried to reproduce, but having heavy issues with pulling the keycloak image, either the tls handshake to quay fails directly or pulling some layers eventually times out. Has anyone experienced similar issues before?
Anyway, I think I have found the the problem with multiple slf4j binding, but not sure why it just manifest in the concrete example, will further investigate later today.

@mshima
Copy link
Member Author

mshima commented Dec 30, 2023

Fixed with 3.2.1 support.

@mshima mshima closed this as completed Dec 30, 2023
@deepu105 deepu105 added this to the 8.2.0 milestone Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants