Mark, On 11/6/13, 11:58 AM, Mark Thomas wrote: > On 06/11/2013 16:49, Romain Manni-Bucau wrote: >> it is too long. >> >> If I try to summarize the execution of tests here what the user feel: >> >> 1) tomcat starts (ok a bit "long") -> understandable so OK >> 2) tests are executed (~ fast if you don't abuse of shrinkwrap things) -> OK >> 3) tomcat shutdown (after tests) -> KO: the server doesn't anything >> more (no more requests to process) but is waiting for its executor to >> shutdown > > Thanks, I think I understand now. > > There should only be a delay at point 3 if the server is still doing > something otherwise the executor shut down should be pretty much > immediate. If the executor is taking a noticeable time to shut down then > it would be worth looking at what the threads are doing. > > If memory serves me correctly, this was added to enable a more graceful > shutdown of WebSocket connections when the server and/or connector were > stopped.
It could also be a server socket waiting for a read-timeout to occur on a keepalive request, right? Disabling keepalives in the "tests" could eliminate the problem (if that's what it is). -chris
signature.asc
Description: OpenPGP digital signature
