question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Spring Boot 3 Native `nativeCompile` Fails to Set `ReactiveTypeHandler#isContextPropagationPresent`

See original GitHub issue

Bug Report for Spring Boot 3 Native (GraalVM 22.3) Having a simple Spring Boot application (generated on start.spring.io) building the native image (via ./gradlew nativeCompile) fails to “process field ReactiveTypeHandler#isContextPropagationPresent” due to “SLF4JServiceProvider: LogbackServiceProvider not a subtype” error which doesn’t make sense since the class is a subtype of the provider. The full log message is:

...
> Task :nativeCompile
...
Field org.springframework.core.ReactiveAdapterRegistry#mutinyPresent set to false at build time
Processing of field org.springframework.web.servlet.mvc.method.annotation.ReactiveTypeHandler#isContextPropagationPresent skipped due the following error : org.slf4j.spi.SLF4JServiceProvider: ch.qos.logback.classic.spi.LogbackServiceProvider not a subtype
Field org.springframework.boot.autoconfigure.web.format.WebConversionService#JSR_354_PRESENT set to false at build time
...

Also adding the io.micrometer:context-propagation doesn’t change anything, still same error log.

To be clear, I’m not fully sure what are the consequence of the above, since I’m new to GraalVM. I’m filling this since the field seems to be directly in the handler. Also I’m not sure where exactly I need to post this issue. There’s so many moving parts 🙂 here. Apologies in advance. Let me know if I need to provide more information. Thanks.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
sdeleuzecommented, Oct 31, 2022

Thanks, no need, I will handle it via https://github.com/spring-projects/spring-framework/issues/29406, you can close this issue on Boot side I think.

1reaction
mhalbrittercommented, Oct 31, 2022

Interesting, can reproduce. @sdeleuze Any idea?

It doesn’t break the build, it’s “just” a warning. We should fix it nonetheless.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Native Support in Spring Boot 3.0.0-M5
If the application builds successfully but fails to start, it is likely that some reachability metadata is missing. The need for it can...
Read more >
Buildpacks Error collecting native-compiler info #1642 - GitHub
I am always getting the same error when trying to build native ... -databind-2.13.3.jar:/workspace/BOOT-INF/lib/spring-jcl-5.3.20.jar:/ ...
Read more >
Go Native with Spring Boot 3 and GraalVM - Java - Oracle Blogs
Short "how to" build a simple web application using Spring Boot 3 ... to create a simple web application, compiled to a native...
Read more >
Going Native With Spring Boot 3 GA - Better Programming
The spring-boot-starter-parent declares a native profile that configures the executions that need to run to create a native image. You can ...
Read more >
Native Images with Spring Boot and GraalVM - Baeldung
Any other usage must be announced to the AOT compiler, which the Native Image builder tries to reach by performing static code analysis....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found