You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2006/04/18 01:10:21 UTC

DO NOT REPLY [Bug 39329] New: - mod_dbd ap_dbd_acquire failure

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329

           Summary: mod_dbd ap_dbd_acquire failure
           Product: Apache httpd-2
           Version: 2.2.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other Modules
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: mkent@magoazul.com


I'm using mod_dbd with persistant mysql connections and another custom module to
do vhost document root lookups against a database. 

The problems is that my mod_dbd connections reach the MySQL daemons wait_timeout
of 600 seconds and are closed automatically. ap_dbd_acquire fails for these
resources and returns NULL which leaves me without a db connection to work with.

Attached is a suggested patch to invalidate the bad resources and try to acquire
another a good one, which should be a newly opened and valid connection.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From mkent@magoazul.com  2006-05-18 18:16 -------
(In reply to comment #6)
> Just revisiting this, I hacked (In reply to comment #0)  
> > I'm using mod_dbd with persistant mysql connections and another custom  
> module to  
> > do vhost document root lookups against a database.   
> >   
> > The problems is that my mod_dbd connections reach the MySQL daemons  
> wait_timeout  
> > of 600 seconds and are closed automatically.  
>   
> Come to think of it, I thought mysql_ping (as used in the check_conn function)  
> would reopen the connection if it had timed out.  ISTR it doing that for me  
> when I tested it.  
>   
> Adding a new patch (untested).  Not decided whether to test and commit it. 

Just tested the latest patch and it almost works but bumps into an issue I've
run into with mysql before: when a connection is closed the first mysql_ping
will always fail and the handle needs a second command to actually reopen the
connection despite what the manual says
(http://dev.mysql.com/doc/refman/5.0/en/mysql-ping.html). Made a slight change
to your patch and its working fine in testing so far.

Also, as noted in the manual page, as of 5.0.3 MYSQL_OPT_RECONNECT is not on by
default, the driver needs to set it after mysql_init like

mysql_options(&mysql, MYSQL_OPT_RECONNECT, &my_true)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329


apache.ei@kefro.st changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |apache.ei@kefro.st




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From mkent@magoazul.com  2006-04-18 22:52 -------
(In reply to comment #4)
> DBDKeep is surely a maximum.  The problem in question isn't going to apply to 
> servers around peak load. 
>  
> The implication of looping would seem to be tearing down and opening lots of 
> connections all at once - could be a Bad Thing.  IMHO A better fix - which 
> alas can't be easily retrofitted - would be to return an EAGAIN status and 
> leave the application to retry. 

That would be nice.

Just to give you an idea of how your code is being used; these servers are under
fairly heavy load but the lookup results are stored in memcached and eventually
the db connections begin to idle long enough to get killed off. Then every
minute or so a bad resource is acquired and nuked, adds a bit of fluff to the
error log, but works pretty well overall. 

Thanks for looking at this so quickly.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd reconnection and prepared statements

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From daniel@bestningning.com  2007-08-22 07:33 -------
(In reply to comment #11)
> Just retested this with mod_dbd from trunk (r553563) and apr-util 1.2.7 +
> current apr_dbd_mysql.c compiled against MySQL 5.0.27 and everything works as
> expected with no modifications. Reconnection no longer seems to be an issue 
as
> the need for 2 mysql_pings seems to have dissapeared, see the last couple 
replies in
> http://bugs.mysql.com/bug.php?id=9271
> but I believe for any earlier MySQL versions it will still be required. 
> Now the bad part is since mysql_ping in MySQL 5.0.27 (5.0.20 and later I 
think)
> doesn't return an error anymore, just reconnects transparently, and since
> prepared statements are cleared as per 
> http://www.mysql.org/doc/refman/5.0/en/auto-reconnect.html 
> I'm not sure how you can detect that a mysql_ping has done a reconnection and
> reinit your prepared statements. I suppose you'd need to track the id of the
> mysql connection and look for a change before and after calling 
apr_dbd_check_conn.

I tried the patch and found something might be a performance issue. this part 
of the patch :

+        if ((rv == APR_SUCCESS) || (rv == APR_ENOTIMPL)) {
+            rv = dbd_prepared_init(pool, svr, rec);
+            break;
+        }

gets executed even if the first apr_dbd_check_conn returns a success. Is this 
on purpose? 


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329


jorton@redhat.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Other Modules               |mod_dbd




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd reconnection and prepared statements

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329


mkent@magoazul.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|mod_dbd ap_dbd_acquire      |mod_dbd reconnection and
                   |failure                     |prepared statements




------- Additional Comments From mkent@magoazul.com  2007-07-06 18:33 -------
Just retested this with mod_dbd from trunk (r553563) and apr-util 1.2.7 +
current apr_dbd_mysql.c compiled against MySQL 5.0.27 and everything works as
expected with no modifications. Reconnection no longer seems to be an issue as
the need for 2 mysql_pings seems to have dissapeared, see the last couple replies in

http://bugs.mysql.com/bug.php?id=9271

but I believe for any earlier MySQL versions it will still be required. 

Now the bad part is since mysql_ping in MySQL 5.0.27 (5.0.20 and later I think)
doesn't return an error anymore, just reconnects transparently, and since
prepared statements are cleared as per 

http://www.mysql.org/doc/refman/5.0/en/auto-reconnect.html 

I'm not sure how you can detect that a mysql_ping has done a reconnection and
reinit your prepared statements. I suppose you'd need to track the id of the
mysql connection and look for a change before and after calling apr_dbd_check_conn.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From nick@webthing.com  2006-05-08 00:09 -------
Created an attachment (id=18244)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18244&action=view)
Patch to retry a problem connection


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From rpluem@apache.org  2006-04-18 21:03 -------
(In reply to comment #2)

>  
> I think I'd be happy with a variant on the patch that keeps a count and bails 
> out explicitly if things get silly.  Anyone else? 

Sounds reasonable to me. What about about the maximum number of entries in the
resource list as upper limit for the counter?



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From mkent@magoazul.com  2006-05-18 18:18 -------
Created an attachment (id=18318)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18318&action=view)
now with two connection checks


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329


nick@webthing.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |PatchAvailable




------- Additional Comments From nick@webthing.com  2006-05-08 00:06 -------
Just revisiting this, I hacked (In reply to comment #0)  
> I'm using mod_dbd with persistant mysql connections and another custom  
module to  
> do vhost document root lookups against a database.   
>   
> The problems is that my mod_dbd connections reach the MySQL daemons  
wait_timeout  
> of 600 seconds and are closed automatically.  
  
Come to think of it, I thought mysql_ping (as used in the check_conn function)  
would reopen the connection if it had timed out.  ISTR it doing that for me  
when I tested it.  
  
Adding a new patch (untested).  Not decided whether to test and commit it. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From nick@webthing.com  2006-04-18 01:34 -------
I'm not sure this is safe: the potential problem is that your while() loop 
never terminates, if some backend returns SUCCESS on acquire but some other 
status on check_conn.  I can't think of a realistic case, but that's not the 
point. 
 
I think I'd be happy with a variant on the patch that keeps a count and bails 
out explicitly if things get silly.  Anyone else? 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd reconnection and prepared statements

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From daniel@bestningning.com  2007-09-11 19:44 -------
Created an attachment (id=20794)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=20794&action=view)
mod_dbd.c patched to invalidate the reslist of all stale connections

The mod_dbd.c is taken from the trunk before being patched. It simply recreate
a resource if all the connection resource in a reslist fail check_conn.
Re-prepare the statement doesnt seem to completely fix the problem as
mysql_ping doesnt seem to restore the connection handle either. Re-create all
resource wont be a problem because it only happens once for every idle timeout.
this patch requires auto-reconnect to be turned off for mysql. Now it works on
all my servers. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd reconnection and prepared statements

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329


rpluem@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From rpluem@apache.org  2007-09-12 11:48 -------
Please provide a patch instead of the full mod_dbd.c (see also
http://httpd.apache.org/dev/patches.html)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From mkent@magoazul.com  2006-04-17 23:11 -------
Created an attachment (id=18116)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18116&action=view)
patch to retry for a valid connection


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329


apache.ei@kefro.st changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #18318|0                           |1
        is obsolete|                            |




------- Additional Comments From apache.ei@kefro.st  2006-10-11 04:50 -------
Created an attachment (id=18989)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18989&action=view)
Reprepare Statements after autoreconnect

This patch adds one line attempting to recreate prepared statements after a
reconnection. This appears to fix the issue, although more errorchecking may be
neeeded.
(Patch is working nicely on 2.2.3).


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329


chetanreddy@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chetanreddy@gmail.com




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329


poeml@suse.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |poeml@suse.de




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


DO NOT REPLY [Bug 39329] - mod_dbd ap_dbd_acquire failure

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39329





------- Additional Comments From nick@webthing.com  2006-04-18 22:05 -------
DBDKeep is surely a maximum.  The problem in question isn't going to apply to 
servers around peak load. 
 
The implication of looping would seem to be tearing down and opening lots of 
connections all at once - could be a Bad Thing.  IMHO A better fix - which 
alas can't be easily retrofitted - would be to return an EAGAIN status and 
leave the application to retry. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org