J
Jens Dahlin
Guest
I have a locking issue where it seems that one query is locking a record used in another (concurrent) query. The locking issue definitely occurs and is also nicely handled with NO-WAIT etc. However looking at the queries it seems that the locked record should not be in scope in the first query. The where clauses used should see to that. Can the locking "scope" be bigger than the actually returned records? Is this dependant on the index usage in the query or something else? XREF compile show at least decent, if not perfect, index usage in the respective queries. Concurrency is handled by the appserver and async calls. OE11.7.4 on Ubuntu Linux.
Continue reading...
Continue reading...