in ur jrun.xml
<service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService">
<attribute name="activeHandlerThreads">8</attribute>
<attribute name="minHandlerThreads">1</attribute>
<attribute name="maxHandlerThreads">1000</attribute>
<attribute name="mapCheck">0</attribute>
<attribute name="threadWaitTimeout">20</attribute>
<attribute name="backlog">500</attribute>
<attribute name="deactivated">true</attribute>
<attribute name="interface">*</attribute>
<attribute name="port">51010</attribute>
<attribute name="timeout">300</attribute>
Apache spawns a child process on every request to perform this mapping
lookup if it's NOT set to zero.
HTH!
Stace
_____
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: October 16, 2003 9:49 PM
To: CF-Talk
Subject: Apache issues with CFMX 6.1
I've been having a lot of problems with the JRun connector to Apache of
late. I'm running CFMX 6.1, Apache 2.0.47, and RedHat Linux 8.0 on a
dual
Xeon with a gig of RAM. Aside from a couple ssh sessions, there is
nothing
else running on it.
I'm using http_load against the server at 85 requests per second for a
collection pages and static files. In general, everything seems normal
from
the outside (though the log is filling up). However, occasionally
Apache
locks up, spikes to 100% of one CPU, and hamstrings CF. It seems to be
tied
to the listener thread / segfault errors seen below. Apache is just
spinning it's wheels under that load, no work at all, so I strongly
suspect
it's the connector that's having issues.
The apache error_log is full of errors I don't really understand from
the
JRun connector:
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
