or help and sorry for the noise !
regards
roland
ps:
and indeed this should not be named memory leak, as a memory leak means
indefinite ressource grow...
> Gesendet: Sonntag, 05. Juni 2016 um 20:14 Uhr
> Von: "Mark Thomas"
> An: "Tomcat Users L
On 04/06/2016 09:22, devz...@web.de wrote:
> thanks for help - but, are you really sure?
Yes.
> if i
>
> - set development=false
> - delete everything within work subdir to force recompile of every jsp
>
> then for me, the initial crawl makes jvm consume the same amount of memory
> regardless
thanks for help - but, are you really sure?
if i
- set development=false
- delete everything within work subdir to force recompile of every jsp
then for me, the initial crawl makes jvm consume the same amount of memory
regardless development true or false - and thats what i'm wondering about.
On 03/06/2016 17:14, devz...@web.de wrote:
You are NOT observing a memory leak.
> Regardless we have set "development" to true or false in
> conf/web.xml, , whenever i recursively crawl our website with wget
> (cleaning work dir before to make sure each page is being compiled
> again), i can ea
hi,
we have a problem with our website for a while.
I tracked it down to a memory-ressource-issue due to memory-requirements for
compiling.
We can throw memory at the problem to circumvent it, but it looks weird to me.
Regardless we have set "development" to true or false in conf/web.xml, ,
