Users might get out-of-memory (OOM) in Java application and suspect that the issue may be caused by Java 17: resource.isReadable() with concurrency leaks large amounts of non-heap memory. Looking for confirmation on whether the issue has been fixed in commercial versions of Spring Framework.
Spring Framework
The issue has been fixed only as of Spring Framework 6.1.1, so any lower versions, such as Spring Framework 5.3.41, does not contain the related optimization.
It is suggested to upgrade to Spring Framework 6.1.1 or later to get the optimization.