Hi,
this seems also to be a problem in mod_jk , tomcat4.1.10, apache 1.3 on
a linux server however it does build up slowly over the day.
The problem seems to be that the connection via mod_jk (Port 8009) does
not close, so the java/tomcat processes
will not quit after responding to the request
Hi Christoph,
I would recommend to upgrade to Apache 2 and mod_jk2 as soon as
possible. With the old Apache 1 and mod_jk we had a whole set of other
problems when it came to load related instabilities. The new version is
heaps better.
Lars
Christoph Fischer wrote:
Hi,
this seems also to be a
David,
Checking my log files, I can see that I get many of thoe lines in the
generic apache error log:
[...timestamp...] [error] child process xyzabc still did not exit,
sending a SIGKILL
I get at least 40 of these just after it starts running full. That does
not look ok, does it?
Lars
David
Hi,
We have an odd problem we cannot solve. Maybe someone else has come
across this too.
We use Apache 2.0.52 with the Tomcat 5.0.25 and its included mod_jk2
with Coyote/JK2 AJP 1.3 connector.
Usually Apache uses 230 slots out of 1000 it has set as the maximum.
This can be seen from the
I would start with the apache logs and find out what kind of requests
are logged in the access just before the event. That should get you
going in the right direction.
--David
Lars George wrote:
Hi,
We have an odd problem we cannot solve. Maybe someone else has come
across this too.
We use
David,
This proves more difficult, since the requests look like standard
requests that work at other times. Moreover the POST data is no logged
anyway so I cannot check if it was a value that was sent in by chance.
Is there anything else I can check to see what is going on? I was more
thinking
Hmmm.. My assumption to your email was their was some kind of possible
probing of your Apache server and/or a misbehaving client. Do you run
snort on the box hosting the Apache httpd service? It's an intrusion
detection tool designed to log suspicious activity. That could be
something to
