Hi,
We are currently facing the same problem (Deadlock found when trying to
get lock; Try restarting transaction)
in our production environnement. We are using InnoDB tables (mysqk
3.23.48-max) with
Jboss 2.4.4 and JDBC driver mm.mysql-2.0.11-bin.jar / RedHat 7.1.
Could you please tell me how to f
all COMMIT to release the locks.
> JDBC Driver: mm.mysql-2.0.6.1.jar
> MySQL: mysql-max-3.23.42-win
>
>Thanks,
>
>Erik
Regards,
Heikki
http://www.innodb.com
>-Original Message-
>From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
>Sent: Friday, October 19, 2
e. PLEASE HELP!
JDBC Driver: mm.mysql-2.0.6.1.jar
MySQL: mysql-max-3.23.42-win
Thanks,
Erik
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 19, 2001 3:11 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: innodb problem (
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,
Heikk
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 100 locking error, as if the
previ
