It's not a secret anymore!
The moose likes JDBC and Relational Databases and the fly likes row level lock issue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "row level lock issue" Watch "row level lock issue" New topic

row level lock issue

Nevin kumar
Ranch Hand

Joined: Mar 15, 2008
Posts: 93
1. autocomit set to true
2. transaction isloation level set to none
3. two statements executed . one does read on a row. the second one does update on the same row.
4. we donot close the connection.
5.Using a database client, we check using a select that the row was correctly updated.
6. do a update on the same query using the database client (such as toad)
7. the update query keeps running forever.

Looks like a lock on that row is being held but no idea who is holding and why? any clue?
Paul Sturrock

Joined: Apr 14, 2004
Posts: 10336

How have you managed to set transaction isolation level to none? This is only going to apply if you are using a database that does not support transactions. I can only think of two database (Access and MySQL's MyISAM database engine) that allow data access without transaction; are you using either of those?

JavaRanch FAQ HowToAskQuestionsOnJavaRanch
I agree. Here's the link:
subject: row level lock issue
It's not a secret anymore!