By default, Tomcat and mod_jk leave the Sockets open between them
indefinitely. The usual way to work around this is to configure a
connectionTimeout in the element, and possibly enable
cping/cpong on the Apache side. In any case, Tomcat doesn't expose the
socket to the webapp, so there isn'
Hi James,
Maybe the webapp clients exceed the maximun allowed by OS. You have to
increase the number of open files for tomcat launch user.
add
ulimit -n 32000
into tomcat's launch script.
hope this is helpful
James Johnson ha scritto:
> I have a Spring based application that is running in T
I have a Spring based application that is running in Tomcat 5.5.12. Tomcat
is integrated with Apache. Apache host JavaScript client side code that
makes Http asynchronous calls to the Spring based application. I'm getting
an error reported from Apache as follows:
Too many open files: apr_accept:
