Good Day
We see lock errors on the Astea Alliance application and were wondering if any once can clarify, describe the differences between the:
LOCK_OPTIMISTIC
And
DISABLELOCK
errors?
Solved
Astea locking: LOCK_OPTIMISTIC And DISABLELOCK
Best answer by Gene Maltepes
LOCK_OPTIMISTIC - this is a standard lock optimistic error where 2 users/processes are trying to access the same record for updates simultaneously. The lock should be released, and the submission should succeed upon retry. You can always check the ‘ap_lock’ table in the database for locks that may be hanging around longer than they should.
DISABLELOCK - usually accompanied with the error ‘System error occurred. Contact your System or Database Administrator’. I escalated it as a known standard issue with our R&D for more explicit error handling occurring on the Alliance Framework level.
LOCK_OPTIMISTIC - this is a standard lock optimistic error where 2 users/processes are trying to access the same record for updates simultaneously. The lock should be released, and the submission should succeed upon retry. You can always check the ‘ap_lock’ table in the database for locks that may be hanging around longer than they should.
DISABLELOCK - usually accompanied with the error ‘System error occurred. Contact your System or Database Administrator’. I escalated it as a known standard issue with our R&D for more explicit error handling occurring on the Alliance Framework level.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.