DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27143>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27143 provide a "low in memory" concept Summary: provide a "low in memory" concept Product: Tomcat 4 Version: 4.1.27 Platform: Other URL: http://jakarta.apache.org/tomcat/faq/memory.html OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] reading the FAQ, tomcat users appear to be quite "blind flying" when it comes to memory management. In my web application, I am trying to move really large files through to mysql (45MB and alike - see http://bugs.mysql.com/?id=2916 for more). Under such circumstances, it is not so surprising that out-of-memory situations can occur. In order to make such an application more predictable, it would be great to be able to manage this more proactively. Suggestion: =========== it would be great if there was a call-back from tomcat warning me if remaining space gets below a configurable level. This way, the application could iterate through the current sessions and for example kick-out the ones with the longest idle time until a traget free memory level is available again or it could throw out objects hanging in such sessions that are larger than say 4 MB, etc... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
