I'm doing about 200,000 inserts, collecting them into batches of 500, and queuing them into a thread pool with 6 threads.
R. -----Original Message----- From: Ady Wicaksono [mailto:[EMAIL PROTECTED] Sent: Monday, February 20, 2006 8:36 PM To: Robert DiFalco Cc: mysql@lists.mysql.com Subject: Re: Lock wait timeout exceeded during concurrent inserts on an InnoDB table.... Roberts How many concurreent inserts you've done? What MySQL version you use? > Concurrent inserts (there also may be concurrent reads going on) are > intermittently causing: > > java.sql.SQLException: Lock wait timeout exceeded; try restarting > transaction > > I noticed that adding innodb_table_locks=0 in my.ini fixes the problem. > Looking through the manual however, this should only be a problem when > I am using LOCK_TABLE, but there is no where in my code that I use this. > Do some queries implicitly add LOCK_TABLE? Is there a way to disable > innodb_table_locks when I create my database or in some JDBC property > so I don't require users to modify their my.ini files? > > FWIW, I'm guessing this is a bug; i.e. hat innodb_table_locks controls > more than just the locking behavior of an explicit LOCK TABLE. > > R. > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
