Hi SAm, I actually had a similar problem myself, but was unable to prove it was the persistent connection itself causing this. I'm wondering if this means that INNODB thinks that a connection that is now 'sleeping' (ie. where a connection was created, used, but is now unused but still open) might be locking the whole table erroneously for some reason? Which version are you using? I could not figure out why Innodb would think the table was locked, other than if someone specifically said 'LOCK TABLE' in a query, which wasn't the case.
Any thoughts? John Sam Lam wrote: > I recently switched to InnoDB & persistent connections from PHP. > > Lately I've been getting these errors "Lock wait timeout exceeded; Try > restarting transaction" on an UPDATE on table. The system is in > development so there is at most one other user ( a back end Perl script). > > When I switched PHP back to non-persistent connections I stopped getting > that error. > > How does one use persistent PHP connections & InnoDB to avoid this error ? > > > --------------------------------------------------------------------- > 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 > > . > --------------------------------------------------------------------- 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
