The cleanly setup system didn’t solve our problem. So now, we are exploring the following changes, as recommended by the resources I have listed in my earlier entry:
- review settings in jrun.xml
- upgrade jvm
Reviewing jrun.xml
The following extracts show the current settings in our jrun.xml:
<service class="jrun.servlet.http.WebService" name="WebService">
<attribute name="port">8500</attribute>
<attribute name="interface">*</attribute>
<attribute name="deactivated">true</attribute>
<attribute name="activeHandlerThreads">200</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="timeout">300</attribute>
</service>
<service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService">
<attribute name="activeHandlerThreads">25</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">false</attribute>
<attribute name="interface">*</attribute>
<attribute name="port">51010</attribute>
<attribute name="timeout">300</attribute>
<!-- set this to false for multi-hosted sites -->
<attribute name="cacheRealPath">false</attribute>
We have changed the settings as follows:
<service class="jrun.servlet.http.WebService" name="WebService">
....
<attribute name="activeHandlerThreads">100</attribute>
<attribute name="minHandlerThreads">5</attribute>
<attribute name="maxHandlerThreads">300</attribute>
....
</service>
<service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService">
<attribute name="activeHandlerThreads">100</attribute>
<attribute name="minHandlerThreads">5</attribute>
<attribute name="maxHandlerThreads">300</attribute>
....
</service>
