On 4/25/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Do you have a small test case, if nothing else, your connections should eventually timeout and that should recycle the processors. As long as the comet connection is active, the processor is spoken for.
He submitted a test webapp that generated a full response asynchronously, but I don't see anything which wouldn't cause the client to just "sit there" after the response is sent. As a result, I don't see any way to get an IO event (unless the client disconnects - which happens if there's a Connection: close header -, the client sends a subsequent request, or a timeout occurs). Rémy --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
