Remy Maucherat wrote:
-1. There is no memory leak with this. ByteChunks/CharChunks are always reused. If new ones are created, they will be reused.
Arg, I have to find something. I know ! It's all Costin's fault !
I didn't think about the "scaling back" feature of the thread pool, to be honest. It should be very easy to avoid the problem, by setting maxSpareThreads to maxThreads.
Also, Jk-Coyote doesn't pool threads, so the total number of Requests created will (slowly) grow over time.
I'm almost certain JK doesn't register the RequestInfo objects. It should (and it's a bug), but actually it doesn't. I tried to have the status servlet work with JK also, and had partial fixes, but in the end, I didn't find the feature too worthwhile (and my fixes were hacks), so I forgot about it (good thing I did).
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
