https://bz.apache.org/bugzilla/show_bug.cgi?id=69567
--- Comment #2 from Yass <yosr.hmo...@prostep.com> --- Thank you for your response. While I understand that cache eviction failures should not impact the resource serving process itself, in my case, the behavior is slightly different. The application works as expected when I increase the cache size (cacheMaxSize="104857600"). The issue seems to occur specifically in Apache Tomcat versions 10.1.32, 11.0.1 and 11.0.2. With versions earlier than 11.0.1, I am not seeing this behavior. Steps to Reproduce: -Start Tomcat 11.0.1 or 11.0.2. -Set cacheMaxSize="1024" in the application's context.xml: <Resources cacheMaxSize="1024"/>. -Deploy an application serving large resources (e.g., JS files). -Tomcat returns 200 OK, but the resource is missing (no content). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
