Howdy,

>Sorry - I was trying to use tomcat 4.1.29 and never looked at 5.0 docs.

The same is documented in the places I mentioned for the tomcat 4.1
versions, e.g.
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jasper-howto.html.

>In 4.1 ones there are really vague advices regarding memory ;-(
>Also the 4.1.x was for quite a long period of time regarded as "stable"
>- not very stable with the default setting.

It's still "regarded as stable", including with the default setting.
Just not developed as much, only bug/security fixes.

>Come on! That was an isolation test case. Of course this is not a
>production system. On the production system we have approx 20-30 jsps
>with headers being updated (XMLs fetched and transformed) from another
>service once in an hour. But this system could stay up no longer than 2
>days. If I new that the compilation is a problem I would do it
otherwise
>- but I have suspected our code with the leak. Tried to use insane
>(http://performance.netbeans.org/insane/) to find the leak and found
the
>tomcat buffers ...

So you have an application running on a server that for some reason has
a memory leak.  This is not a rare problem.  You try to track it.  You
can use a bunch of tools and analyzers, and maybe find the solution
yourself.  Or you can try to search the documentation first, which as I
mentioned contains information about this issue in several very
prominent and easy to find spots.

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]

Reply via email to