I believe this is called the pseudo closing of locks. SQL "soft closes" the
file as it thinks you are going to read from it again soon.
ALCOBJ CONFLICT(*RQSRLS) can remove the locks.
Not sure if there is any other way around it.
May be a google of pseudo close might reveal more.
Regards
Neill
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Davor
Sent: 19 March 2010 23:45
To: Java400 mailing list
Subject: Locks are held... never released...
Hi there...
we're having some problems with shared read locks on AS400 V5R4, accessed
with jt400.
The problem is described here
http://stackoverflow.com/questions/2476470/db2-jdbc-driver-does-not-release-
table-locks
To cut the story short,
- we (Spring) issue an update statement, and table obtains a shared read
lock (normal)
- after we close the statement, the lock is still there (i guess normal)
- after we commit, the locks disappears (normal)
- then, when we issue a SELECT statement, the lock re-appears... and
after closing the ResultSet, Statement, and Connection (Spring does
that),
the lock remains (NOT normal)
Do you have any idea, some kinda clue - where is the source of these "never
going away locks"? These are shared read locks, and they don't affect our
application and user experience in no way, but from time to time, we have to
issue some ALTER TABLE statements, and with these locks, we can't.
Thank you very much,
Davor
midrange.com
