We all have encountered this kind of problem with socket
implementation (derived from the good old known BSD).
The only solution is to close the socket to have the read
aborted and so the thread awaiked ;(
And I don't speak about writing on half-closed socket where
you get no error for a while
>
> I am using Apache mod_jk and Ajp13 to connect to Tomcat 4.
> When shutting down Tomcat 4 it takes about 15 seconds when
> using apache for the tomcat process to complete,
> when using Tomcat 4 standalone shutdown and termination of
> the process happens almost immediately.
>
> Has anyone el
uOn Tue, 8 Jan 2002, Kevin Seguin wrote:
> i think Ajp13Connector and Ajp13Processor are more complicated than they
> need to be. but, that's just thought :)
I'll check in the jk2 version of the 4.0 connector - it seems to work
fine ( using ThreadPool and C2B and all the nice stuff ), but I hav
> Now the question is...
>
> How hard would it be to get the worker threads to block on either the
> socket OR some type of shutdown event, with either satisfying
> the wait?
>
ideally :) i think the problem might be that once you're blocked reading on
a socket, other than shutting down the s
>
> I am using Apache mod_jk and Ajp13 to connect to Tomcat 4.
> When shutting down Tomcat 4 it takes about 15 seconds when
> using apache for the tomcat process to complete,
> when using Tomcat 4 standalone shutdown and termination of
> the process happens almost immediately.
>
> Has anyone el
