-
Notifications
You must be signed in to change notification settings - Fork 41.1k
BeanCreationException after upgrading from Spring boot 3.3.8 to 3.3.9 #44919
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
Comments
This is unlikely to be a Spring Boot problem as it isn't involved in the creation of CGLib proxies for configuration classes, that's a Spring Framework concern. First of all, please try Spring Boot 3.3.10 as it includes a more recent version of Spring Framework. If that doesn't help and you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue. |
I will try deployment with 3.3.10 |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Getting an exception after upgrading from Spring boot 3.3.8 to 3.3.9 .
Caused by: java.lang.IllegalAccessError: Class 'com.azure.spring.cloud.autoconfigure.implementation.storage.AzureStorageConfiguration$$SpringCGLIB' illegally accessing package-private member of class 'com.azure.spring.cloud.autoconfigure.implementation.storage.AzureStorageConfiguration'
at com.azure.spring.cloud.autoconfigure.implementation.storage.AzureStorageConfiguration$$SpringCGLIB.()
spring-cloud-azure-dependencies : 5.19.0
Java : A custom image built on websphere-liberty:kernel-java17-openj9
Please note it seems to be working fine with OpenJDK 17 .
The text was updated successfully, but these errors were encountered: