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.



-----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

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
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,

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.