You mentioned this solved the problem when using pconnect. I'm using connect, not pconnect so will this still work? Will using pconnect instead of connect do anything for me? Basically everything runs properly but then every once and a while I get a ton of processes that get stuck and send the whole thing to hell... ie many fulltext searches that just die along with other queriest. I'd be happy if I could just set it up so that any connection taking longer than a certain period of time would be killed regardless of if its working on a query or something.
Chris -----Original Message----- From: Arne K. Haaje [mailto:[EMAIL PROTECTED]] Sent: Monday, November 12, 2001 4:29 PM To: Christopher Book Cc: [EMAIL PROTECTED] Subject: Re: 'too many connections' Christopher Book wrote: > > No, I'm not using mysql_pconnect, and my apache configuration seems fine. I > don't have very many users at the moment so there is no reason for the > connections filling up. > > >>This can be due to your apache configuration. do you use mysql_pconnect > function in php. Check you apache setting agains MaxClients StartServers and > etc... > Try adding something like set-variable=wait_timeout=1800 to your my.cnf. We found that when using mysql_pconnect the connections stuck around for far to long. MySQL's default is pretty high for a webserver that gets a few hits. After adding wait_timeout=1800 we have never seen 'too many connections' again. We still use mysql_pconnect. Regards, Arne -- -------------------------------- Arne K. Haaje | T: 69 92 04 90 Enebakkveien 2 | F: 69 92 04 91 1625 Tomter | M: 92 88 44 66 -------------------------------- --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
