n closed exception
in socketinputstream.read() but it takes time to get them. and the delay is
platform dependant. if client abruptly close, TCP/IP protocol has no
information about this except for a very long delay.
Maybe some protocol level tunings like keep alives might help :/
Anyway, this has nothing to do with
, send signal SIGQUIT
to tomcat process, it will force the sun JVM to dump all threads stacks.
Regards,
David Delbecq
Ajit Narayanan wrote:
>
> hi,
>
> My tomcat 4.1.27 is running on sun Solaris 8 box but ocassionally it
> hangs out giving the error " All threads are busy,
hi,
My tomcat 4.1.27 is running on sun Solaris 8 box but ocassionally it hangs
out giving the error " All threads are busy, waiting. Please increase
maxThreads or check the servlet status75". I have tried increasing the no
of threads but its not working I guess. The application code looks cl
