Nikolaos,
thanks for the pointer. I noticed the performance issues while
rendering a site wit about 2MB content. Also it doesn't explain the
leak, it explains the slow performance and memory hunger. Maybe it is
important to mention that I'm using nested layouts. IMHO: Since
stripes handles this
I am aware of the faults with the layout tags. You guys pretty well
understand it, based on what you've written in this thread. Yes, when you
use layout tags the whole contents of the page is cached and then written
out at once. I wanted to fix it for 1.5.2 so that it would stream content to
the
Richard,
As 1.5.3 has only 2 fixes that appear unrelated to this issue... I take
it trying it won't make a difference?
Also I came across this just today - albeit it was initially reported
against 1.4.3 - but it is still OPEN:
http://www.stripesframework.org/jira/browse/STS-391
As far as
Hello List,
while chasing jsp memory leaks I found that using the stripes layout
tag has 3 negative effects:
1. this tag doubles the memory usage in compare to using @include
2. this tag is slow
3. this tag creates memory leaks. after 100 requests (maxThreads = 10
at the ajp processors ThreadPool)
I did notice potential memory leaks
while using older version of Stripes. Do note that I've never actually
investigated since restarting tomcat once in a while seemed to be
rather sufficient solution, but the webapp started to eat memory only
after introduction of Stripes. But after most
