DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33629>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33629 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2005-02-18 11:44 ------- Sorry then, there is no solution. It's basically impossible to prevent webapps from leaking file descriptors, as you see with locked JARs. If you report good experience with using both settings at the same time, then it's good and I can change the docs, but that's all that I can do. What I meant is that I consider using both settings useless (each one introduces a startup performance penalty for the webapp), so I will change the documentation. Note that if "antiJARLocking wasn't powerful enough", then it explains your problems deleting the files in temp. If the files eventually get unlocked, then it's good, but there's nothing I can do in Tomcat about that. I think you should run periodic processes cleaning up leftover stuff in temp. Given the sequential naming of the folders, this should be doable. This cannot be addressed in Tomcat. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
