Hi, >from my point of view there is no reason for the application not to memory >leak >on 4.1.30 but on 5.0.19?
Your point of view is far from completely informed, then ;) (In the literal sense of the word, no insult here). Given the magnitude of the changes between tomcat 4 and 5 it'd be fairly astonishing if their memory profiles were identical. Your specific issue sounds related to the JMX registration thing that's been discussed on this list as a memory leak several times (with a workaround suggested) in the past month. You can also try 5.0.24, which is the latest stable tomcat 5 release. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
