Hi,
I have a script which can burst any number of async socket connections to
Tomcat from a remote host. With it, I can get every available connector
processor thread to become busy at once. At that point, Tomcat simply
refuses any new socket connections at all.
Ok, this is to be expected. But
object for an entire webapp, then I'll check for bugs in my
JDBC driver...
IMHO, if this is NOT a bug in my JDBC driver, then it probably really is a
problem with Tomcat -- sockets simply shouldn't be left in CLOSE_WAIT by an
application.
Thanks,
-Dan
-Original Message-
From: Dan Higgins
Hi again,
It looks like it was a bug in my JDBC driver. Sorry to doubt you marvelous
Tomcat developers of the world.
Cheers,
-Dan
-Original Message-
From: Dan Higgins [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 01, 2003 6:59 PM
To: Tomcat-Dev
Subject: RE: Tomcat 4.0.6
Hi,
Whether it's a bug or not, it's definitely a strange thing going on, and at
this point in time I suspect the mod_jk.so is the problem. I hope I can get
a little verification.
I have a Location Apache directive inside a SSL-enabled virtualhost, and
if I go to a *directory* under that location
