On 18/05/2017 12:20, Abhirama wrote:
As you can see from my post, lock is denied because of "values identity_val_local()" issued by a competing insert on the same table. This is also asserted by the the fact that, in application, if I synchronise all the offending inserts(only inserts, not selects), I do not get a lock exception. I find it really hard to believe that derby locks out on a couple of concurrent inserts.
Oops, sorry, didn't read your post closely enough... -- John English