RE: Innodb Message Lock wait timeout exceeded; Try restarting transaction

2004-09-13 Thread Dathan Vance Pattishall
Basically the application can get this message because another process has a lock on the rows that the delete needs to cover for a time period then your lock_wait_timeout. Is there some cron process? Is the table index properly? What your average query transaction? Active your slow query log to

RE: Innodb Message Lock wait timeout exceeded; Try restarting transaction

2004-09-13 Thread Tucker, Gabriel
when it happened originally. -Original Message- From: Dathan Vance Pattishall [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 2:49 PM To: Tucker, Gabriel; 'Mysql General (E-mail)' Subject: RE: Innodb Message Lock wait timeout exceeded; Try restarting transaction Basically

RE: InnoDB and lock wait timeout

2002-04-06 Thread Daniel Page
Hi, Generally, an apache setup will kill a PHP enabled page when it has run for 30 seconds. Also, when a php script exits, all connections to the database are closed, so somwhere you need to keep the results of your script somwhere (hidden HTML variables, URI string), otherwise, when you change

Re: InnoDB and lock wait timeout

2002-04-06 Thread Michael Bacarella
Hi, On Sat, Apr 06, 2002 at 03:57:39PM -0500, Victor wrote: Suppose that a query begins with begin. Then a couple inserts happen but before the commit statement is executed, the client hits stop in the browser. What is going to do the rollback? If there is a persistent connection, is it