This sounds awfully similar to what we are experiencing, although I have not determined that it is a jk2 related memory leak. Are you using some sort of profiling tool to determine this? And exactly what does request.registerRequests=false do?
Don't know what it does (other than stopping jk2 registering requests, I'd guess)
or why it works. It was mentioned on this very mailing list
a few weeks ago, in response to a previous memory-leak thread, so I tried it and
it worked.
Not very scientific, I know...
Adrian
-- f y cn rd ths y cn gt a gd jb rt fpl dgm pvq!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
