<?xml version="1.0" encoding="windows-1252"?>
<node id="998723" title="Re: Forcing modperl processes to restart after N requests" created="2012-10-12 11:29:35" updated="2012-10-12 11:29:35">
<type id="11">
note</type>
<author id="733061">
flexvault</author>
<data>
<field name="doctext">
&lt;p&gt;&lt;a href="http://www.perlmonks.org/?node_id=892497"&gt;alain_desilets&lt;/a&gt;,&lt;/p&gt;
&lt;p&gt;Have you tested how long it takes to refresh the web-server?&lt;/p&gt;&lt;p&gt;
We have a "slow time" when we refresh all of our high usage servers. We have some persistent Perl applications that we could refresh and the clients waited for the server to respond. Unfortunately with Apache2, mod-perl would go crazy trying to re-connect to the persistent Perl application, which created errors trying to refresh the socket. 
For us, the downtime could be measured in seconds. Refresh didn't work correctly, but we just did a 'stop' followed by a 'start', which worked fine.
&lt;/p&gt;&lt;p&gt;
Just a suggestion.


&lt;/p&gt;
&lt;p&gt;Good Luck&lt;/p&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-733061"&gt;
&lt;p&gt;&lt;b&gt;"Well done is better than well said." - Benjamin Franklin&lt;/b&gt;&lt;/p&gt;

&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
998686</field>
<field name="parent_node">
998686</field>
</data>
</node>
