-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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 is thrown when loading protocol resolvers from ForkJoinPool task #42468
Comments
Thanks for the report. The In the absence of a sample that reproduces the problem, you could test the above theory by patching line 119 of
|
Thank you for the hint. Our Dockerfile looked like this: docs Spring Boot 3.2.0 - Dockerfiles
So But I have updated the Dockerfile based on the latest docs Spring Boot 3.3.4 - Dockerfiles / Source and the issue is gone, works OK. Thank you for the help! Now I'm thinking, I can see the docs for the tools mode were updated in version 3.3.0 - #40094 - which I missed. I believe this feature https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.3-Release-Notes#cds-support was the related one. Does it mean the changes made for the CDS feature caused some incompatibility with the launching the extracted JAR in an older way before 3.3.0 as I had it before? Because now I'm still running the extracted JAR but with |
Yes, that's right. Since 3.3, the extracted jar uses a |
This comment was marked as outdated.
This comment was marked as outdated.
Looking into this and I wonder if we should have a For this failure specifically, I feel like we somehow need to set the classloader that gets used on the actual |
https://github.com/philwebb/gh-42468 reproduces the issue (in a slightly different form) |
I've created #42838 to consider the broader classloader issue so we can target a focused fix for this specific problem in 3.3.x. |
Reopening because I missed the |
…ot-starter-parent to v3.3.5 This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [org.springframework.boot:spring-boot-starter-parent](https://spring.io/projects/spring-boot) ([source](https://github.com/spring-projects/spring-boot)) | parent | patch | `3.3.4` -> `3.3.5` | --- ### Release Notes <details> <summary>spring-projects/spring-boot (org.springframework.boot:spring-boot-starter-parent)</summary> ### [`v3.3.5`](https://github.com/spring-projects/spring-boot/releases/tag/v3.3.5) [Compare Source](spring-projects/spring-boot@v3.3.4...v3.3.5) #### 🐞 Bug Fixes - Running mvn spring-boot:run with classpaths that exceeds Windows' length limits leaves temporary files [#​42841](spring-projects/spring-boot#42841) - Report produced by ConditionReportApplicationContextFailureProcessor is always empty in a failed test [#​42785](spring-projects/spring-boot#42785) - Case-insensitive comparisons may be adversely affected by the user's locale [#​42735](spring-projects/spring-boot#42735) - DataSourceProperties#driverClassIsLoadable should not print a stacktrace to the error stream when it fails [#​42683](spring-projects/spring-boot#42683) - Some `@ControllerEndpoint` and `@RestControllerEndpoint` infrastructure remains undeprecated [#​42498](spring-projects/spring-boot#42498) - Auto-configuration for Rabbit Streams doesn't consider RabbitConnectionDetails [#​42490](spring-projects/spring-boot#42490) - ClassNotFoundException is thrown when loading protocol resolvers from ForkJoinPool task [#​42468](spring-projects/spring-boot#42468) - ActiveMQ Artemis Connection Factory creation fails in native image [#​42421](spring-projects/spring-boot#42421) - Duplicate meter binding when context contains multiple registries, none are primary, and one or more is a composite [#​42397](spring-projects/spring-boot#42397) #### 📔 Documentation - Document that embedded Tomcat must be at least 10.1.25 [#​42849](spring-projects/spring-boot#42849) - Fix systemd example configuration [#​42805](spring-projects/spring-boot#42805) - Document that the exact behavior of the maximum HTTP request header size property is server-specific [#​42789](spring-projects/spring-boot#42789) - Clarify why `@Primary` is recommended when defining your own ObjectMapper that replaces JacksonAutoConfiguration's [#​42787](spring-projects/spring-boot#42787) - Polish javadoc for Binder#bindOrCreate(String, Class) [#​42778](https://github.com/spring-projects/spring-boot/issu...
Hi, we have upgraded Spring Boot app version from 3.3.3 to 3.3.4 and now the SSL bundles cannot be loaded. See the full stack trace of the exception below.
I've found there have been some changes related to SSL bundles in #42119. I can see the key stores are being lazily loaded but not sure how (and if) it can change the class loader that doesn't see
Base64ProtocolResolver
.We have integration
@SpringBootTest
tests that use the SSL bundles and they are successfully passing. So most probably the app must be compiled and packaged as we see those exceptions only when we run the app (built as a JAR) in Docker container. But I could still be missing something.When I downgrade to 3.3.3, it works OK as expected.
I don't have a sample application that reproduces the issue yet.
The app runs on reactive stack.
The text was updated successfully, but these errors were encountered: