Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <025901c7c239$326d0b40$66d482d8@CORP.LOCAL>
Reply-To: "Danie Qian" <daniel@bestningning.com>
From: "Danie Qian" <daniel@bestningning.com>
To: <modules-dev@httpd.apache.org>,
	<Tom.Donovan@acm.org>
References: 
 <00b701c7c000$f2f71300$66d482d8@CORP.LOCAL><1183749481.5095.44.camel@fuego><00d501c7c007$700c0b10$66d482d8@CORP.LOCAL><1183752783.5095.56.camel@fuego><20070706230429.34edfd4a@grimnir><1183772227.5095.70.camel@fuego>
 <20070707093828.618637f7@grimnir> <01a501c7c0ac$e41185d0$66d482d8@CORP.LOCAL>
 <4692418D.8050600@bellatlantic.net>
Subject: Re: mod_authn_dbd - internal server error after certain idle time
Date: Mon, 9 Jul 2007 10:55:31 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="gb2312";
	reply-type=original
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Tom Donovan" <donovant@bellatlantic.net>
To: <modules-dev@httpd.apache.org>
Sent: Monday, July 09, 2007 10:09 AM
Subject: Re: mod_authn_dbd - internal server error after certain idle time


> Danie Qian wrote:
>>
>>
>> It is working a little better now after I set both DBDKeep and DBDMin to
>> zero. But I am still getting the internal server error from time to
>> time. Users usually can get pass the error by reloading the same page.
>> Here is the error messages in the log:
>>
>> [Sat Jul 07 02:56:44 2007] [error] (20014)Internal error: DBD [mysql]
>> Error: Lost connection to MySQL server during query
>> [Sat Jul 07 02:56:44 2007] [error] [client 75.87.112.250]
>> authn_dbd_acquire: Error looking up josiahhansen in database
>>
>
> Unfortunately, DBD connection pooling (which is performed by the
> apr-util reslist facility) presumes that connections last longer than
> DBDTimeout, so just setting DBDKeep and DBDMin will not completely
> eliminate the problem.
>
> The proposed changes to the MySQL driver seem like a good idea and they
> may help - but they will only help MySQL, not any other databases.
>
> I entered a new APR bug and proposed a patch -
> http://issues.apache.org/bugzilla/show_bug.cgi?id=42841
> to change the interpretation of timeout so that it will work to avoid
> this error.
>
> With this patch, setting DBDTimout lower than the MySQL system variable
> 'wait_timeout' will ensure than expired connections never get used.
>

Assuming by DBDTimeout you mean DBDExptime in mod_dbd documentation where it 
implies a keepalive value, how about making mod_dbd to send something to 
mysql server so that its wait_timeout timer gets reset whenever the 
keepalive time elapses? Is this what the setting originally meant for?
As I am pretty new to this listing and I apologize if I am not on the same 
page as you guys.