https://bz.apache.org/bugzilla/show_bug.cgi?id=60963
--- Comment #25 from Mark Thomas <ma...@apache.org> --- Having looked into this further, the only way I could see to improve things significantly was to pre-process the JAR files from a packed WAR and populate the cache with the contents of the JARs. This wasn't a great solution for several reasons: - It would have required a fair amount of new code and/or a lot of refactoring - The memory requirements for the cache would increase. For the solution to be useful, all the contents of all the JARs need to reside in the cache. In the end, I opted to implement a new WebResourceRoot implementation, ExtractingRoot that returns to the 7.0.x idea of extracting the JAR files into the work directory. This will be included in 9.0.0.M25 onwards. Assuming no issues are identified, I'll back-port it to 8.5.x and 8.0.x. An open question is whether the overall refactoring of resource handling is sufficient to protect against the file locking issues. -- 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
