Skip to main content
Solved

Astea locking: LOCK_OPTIMISTIC And DISABLELOCK

  • August 30, 2021
  • 1 reply
  • 114 views

Forum|alt.badge.img+1

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?

Best answer by Gene Maltepes

@LisaRochoy, @k.bilsland ,

 

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.    

 

 

View original

1 reply

Forum|alt.badge.img+1
  • Do Gooder (Employee)
  • 10 replies
  • Answer
  • October 20, 2021

@LisaRochoy, @k.bilsland ,

 

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.    

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings