Erik, run the MySQL server mysqld from a command prompt and do with the mysql client:
mysql>create table innodb_lock_monitor(a int) type = innodb; (assuming you run a recent version). Then mysqld will print lock information to the standard output and you see what is happening. Regards, Heikki http://www.innodb.com/ibman.html >Has anyone encountered locking problems using JDBC with InnoDB tables and >transactions? I am wondering if the MySQL JDBC was designed to handle >transactions properly since InnoDB is a relatively recent addition to MySQL. >The problem I am running into is the 1000000 locking error, as if the >previous transaction hasn't committed. > >What complicates this is that I am using Bean Managed Persistance (BMP) with >container managed transactions with JBoss as my EJB container. This means >that I don't actually write the transaction code, so it's hard to tell >exactly what's going on. A transaction is generally defined by the >container as each method call that the client makes. > >I have the transaction option set to "Required" for all the bean's methods, >and the 100000 error occurs when the client makes a second call for the same >table row. An example would be creating a row, then trying to make a second >method call to recreate the same row (resubmitting the JSP page.) This >should return a duplicate row error, but instead produces a locking error, >which the client never sees (shows up on JBoss log.) This makes it seam as >though the lock from the original transaction wasn't released, and perhaps >the database did not even receive or process the COMMIT. > >Is anyone having similar problems, and hopefully found a solution? >Thanks, >Erik --------------------------------------------------------------------- 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
