I'm experiencing this same issue. I've got Tomcat 5.0.27, Apache 2.0.46,
and jk2 version 2.0.4. Has there been any solution? It occurs primarily
under heavy load.
-Joshua Szmajda
We've got a similar issue, though this in on Linux and using channelUnix/JNI instead
of normal tcp channelSocket.
I'm experiencing this same issue. I've got Tomcat 5.0.27, Apache 2.0.46,
and jk2 version 2.0.4. Has there been any solution? It occurs primarily
under heavy load.
-Joshua Szmajda
We've got a similar issue, though this in on Linux and using channelUnix/JNI instead
of normal tcp channelSocket.
Hi Tim,
thanks for the advise.
The interesting part is that tomcat (process) doesn't seem to survive the
re-initialization of the ServerSocket. It this a known bug?
Regards,
Thomas
-Ursprüngliche Nachricht-
Von: Tim Funk [mailto:[EMAIL PROTECTED]
Gesendet am: Dienstag, 15. Juli 2003
We've got a similar issue, though this in on Linux and using channelUnix/JNI instead
of normal tcp channelSocket.
We're using Apache2/mod_jk2 (built from tomcat-connectors-1.1M1).
On heavy load, there are over 3000 sockets open by one Tomcat/JVM, they don't seem to
go down again too while
How do you mean survive? The JVM core dumps (which then is a JVM vendor
issue) or the JVM stays up buit sits there uselessly?
-Tim
Haug Thomas wrote:
Hi Tim,
thanks for the advise.
The interesting part is that tomcat (process) doesn't seem to survive the
re-initialization of the ServerSocket.
