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=38716>. 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=38716 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-20 17:23 ------- As I tried to point out in the inital description, the "resolution" to these problems might lay within libraries that are _not possible_ to reach for a webapp developer. Your suggestion for resolution is then "don't use those libraries"? I had hoped that Tomcat would be pragmatic in this regard, and actually try to supply a server that "works out of the box", given the problems that are present in the environment, even if this is a problem with the core java classes as such. It seems like absolutely no-one that uses Tomcat can get reloading to work properly without getting memory-leaks. The reason for this is rather throughly explained in this enhancement request, and a solutions is proposed. Why is it that you basically just "hate this to death" in such a way? What is generically wrong with being able to "cycle" the threadpools, e.g. by requesting a particular link in the monitor? -- 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]
