Is there some requirement above and beyond the 'return DECLINED' from a PerlTransHandler to allow a thread to terminate normally?

Background: We use a commercial product to produce some of our web content. It has a large number of control parameters that are necessary to its function but of little use to the average user. To make links to our content more manageable we created a perl script to run as a cgi that accepts a minimum of data from the user, combines that with it's own catalog of information and generates the required 400-500 character URL required to produce the desired result. It all works great, except that the cgi basically has to send the result as a redirect, which generates yet another transaction to the server.

We thought, "Wouldn't it be great if we could just do the translation on the fly and save the back an forth?". So we added mod_perl to the system and rewrote the URL script as a PerlTransHandler.

In local testing everything seems to work just fine. We put it out in the world and after just a little bit, the server is sitting idle and Apache has quit responding altogether.

[Sun May 13 20:04:46 2012] [warn] Server ran out of threads to serve r
+equests. Consider raising the ThreadsPerChild setting
[Sun May 13 20:07:44 2012] [warn] (OS 64)The specified network name is
+ no longer available.  : winnt_accept: Asynchronous AcceptEx failed.
[Sun May 13 20:14:39 2012] [warn] (OS 64)The specified network name is
+ no longer available.  : winnt_accept: Asynchronous AcceptEx failed.
[Sun May 13 20:14:54 2012] [warn] (OS 64)The specified network name is
+ no longer available.  : winnt_accept: Asynchronous AcceptEx failed.

[download]
Our environment is: 
Server Version: Apache/2.2.22 (Win32) mod_perl/2.0.4-dev Perl/v5.10.0
Server Built: Jan 28 2012 11:16:39

[download]
We desperately need to do some additional things to protect our server from a lot of spurious traffic, thus our interest in mod_perl, but if we can't get a simple transhandler working it doesn't bode well for other additions to our Apache configuration. If anyone can offer a suggestion as to why the threads under mod_perl are not releasing, it would be greatly appreciated.

In reply to Web Service using mod_perl with PerlTransHandler running out of threads by jswalker

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.