Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <46F5810D.7080708@ice-sa.com>
Date: Sat, 22 Sep 2007 22:54:37 +0200
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: modperl@perl.apache.org
CC: Perrin Harkins <perrin@elem.com>, gozer@ectoplasm.org
Subject: Re: re-post : duplicate sockets with mp2, apache2, linux
References: <46F256BB.9050302@ice-sa.com>
	 <66887a3d0709201409w65801586ib706d1d6ae4ddc45@mail.gmail.com>
	 <46F37529.10700@ice-sa.com>
 <66887a3d0709210403t2e878a65ne4355962f5aad5d2@mail.gmail.com>
In-Reply-To: <66887a3d0709210403t2e878a65ne4355962f5aad5d2@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

-- solved --

My thanks, but also my deepest apologies to anyone who bothered spending 
time considering this post and its predecessor.

There is no voodoo and no problem with duplicate sockets or connections, 
at least not in Apache2 or mod_perl2.  The problem was not in the code 
of my PerlAuthenHandler module either, it was with my setup (and thus 
with me anyway).

For the curious, I was connecting to an external database module, which 
itself connects to a database system.  The problem was that instead of 
telling the external module to connect to the database system, I was 
telling it to connect to itself.  Which caused it to receive ipso-facto 
a second connection request (and log this event), which caused me to 
believe that it was the perl module which was connecting twice.
A classic case of re-reading something 20 times and overlooking the obvious.

AW