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
Failed to open archive entry when dependent Jar is greater than 2GB #28595
Comments
This may be a duplicate of #27822 which was fixed in Spring Boot 2.4.x. Spring Boot 2.2 is no longer supported. Please upgrade to 2.4.x or later and let us know if it fixes the problem. If it does not, please create a small sample project that reproduces the failure and share it with us by zipping it up and attaching it to this issue or pushing it to a separate GitHub repository. |
Thanks for you quick response. You were right. Upgrading the jar to 2.4.11 resolved the issue. At the same time I noticed a more recent version 2.5.4 has the same issue as before. |
Thanks. That's interesting. It should work with both 2.4.x and 2.5.x as the same fixes were made in each branch. If you would like us to investigate the problem with 2.5.x, please create and share with us a small sample project that reproduces the failure. |
Could be because version 2.5.4 was released before this fix was committed. I will see if i can reproduce with a small project. |
Yes, you may need 2.5.5 or later as it contains #27900. |
Yeah that makes more sense now. Closing as the issue is resolved |
Hi Team
I have this project where I have a dependent jar whose size is greater than 2GB. I use the spring-boot-maven plugin to package the application and when starting the application, it immediately fails with the below error. I was able to run the application successfully when this jar was still less than 2Gb but it started failing recently when the size of this jar increased.
Spring Boot Version: 2.2.5-RELEASE
Unfortunately , I'm unable to provide my pom file as this is for an internal project.
I will appreciate any help here.
Thanks.
The text was updated successfully, but these errors were encountered: