No worries, and in all liklihood it isn't an ibatis specific bug, I had just held out hope that someone else might have encountered the issue and arrived at a solution. I've tried both simple and dbcp data sources witht the same results and I'm currently using mysql with innodb tables and row level locking...Just not sure what I might be able to set on the datasource that could have some impact on the situation.
Thanks again for your insight, appreciate it. Koka Kiknadze wrote: > > I bet noone believes it's an iBatis problem. iBatis is database agnostic, > and if there were some general locking issues with inserts/updates they'll > affect every user on this list. > > I've not used MSQL for years, any chance its not using row level locking > in > your configuration? Have you tryed SIMPLE datasource instead of DBCP, or > different JDBC driver? These are things I'd try if I were sure that locks > are not because of bugs in my application, and if looking into ibatis logs > revealed nothing... > > Not quite helpful, sry > > -- View this message in context: http://www.nabble.com/Deadlock-found-when-trying-to-get-lock-%28MySQL-5.0-with-innodb%29-tf2792164.html#a9103064 Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
