Thanks for the tip. We did not set these contex-params. Btw, since we had our problems, there's been several reports about memory leaks in the Jakarta lists as well. It only (AFAIK) shows up with Tomcat 4.1.x.
Our solution was to port the views to Velocity; three days of work and runs like a baby! Eelco ----- Original Message ----- From: "Schnitzer, Jeff" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 02, 2003 4:10 AM Subject: RE: [Mav-user] reusable controllers and session objects > From: Eelco Hillenius [mailto:[EMAIL PROTECTED] > > Second side note: GC can give you problems at times. A recent project > where > we made heavy use of JSTL could crash our server! There is/ are memory > leak(s) in JSTL presumably the forEach tag. The strange thing was that in > certain cases when the GC did a run the JVM ended up using more memory > than > before this run. On several servers (both on Win and Lunix) the memory > usage > could exeed gigabytes within one minute before crashing... FWIW, I haven't seen anything like this on the TSO site. There are a lot of synchronization issues in the Jakarta JSTL implementation, but I haven't seen any memory leaks yet. Make sure you explicitly set the locale and timezone context-params in web.xml - the auto-discovery process tickles a nasty synchronization bottleneck in java.util.Locale. Jeff ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ [INVALID FOOTER] ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ [INVALID FOOTER]
