Re: Problems with INNODB transactions.
Achim Abeling <[email protected]>
| Newsgroups | gmane.comp.db.mysql.java |
|---|---|
| Message-ID | <[email protected]> |
Hi Prasad, did you try to run the innodb lock monitor? The lock monitor gives information about which thread is holding transaction locks. Best regards Achim [email protected] wrote: > Hi, > > I am facing a strange problem with INNODB. My application communicates with mysql server using JDBC. I am using mysql 5.1 version. > > Even after issuing connection.commit() / connection.rollback() commands, still on the sql side the transactions are not getting closed properly. In our application we never try to acquire locks on the same row from different threads. A request is sent only when the previous transaction is closed by issuing commit or rollback. But still the following error is seen : > > "Lock wait timeout exceeded; try restarting transaction". > > The transaction isolation level used is "READ-COMMITTED". We maintain a database connection pool and try to reuse the connections from the pool instead of trying to close and create the connections everytime. In our application there is a continuous database updates happening at a very high rate. > > Could you please suggest what could be going wrong. > > Thanks > Prasad -- MySQL Java Mailing List For list archives: http://lists.mysql.com/java To unsubscribe: http://lists.mysql.com/[email protected]