Yes , Killing the process the is the answer of above question which removes the lock from table in database, but
Offcourse , it will terminate the current process which saves my data into database.
My Scenarion : We are processing policies and we are having concurrentConsumers=20; so while working in concurrent environemnt,
1st consumer will locks the table for manipulation,
2nd consumers will locks the table for manipulation,
3rd consumers will locks the table for manipulation,
4th consumers will locks the table for manipulation,
5th consumers will locks the table for manipulation,
.
.
.
.
and
20th consumers will locks the table for manipulation,
Here, tables are locked so it may be possibility that 5th consumer is waiting for releasing that lock.
So I have to avoid "LockAcquistionException".
Please help me in this.
Many thanks in advance.
Waiting for quick reply.