[Archivesspace_Users_Group] Optimistic locking error

[Galligan, Patrick]

Trevor,

After some help from Mark Triggs, and some digging into logs, it looks like our issue is overlapping login sessions from an application authenticating really often.

-Patrick

From: Galligan, Patrick <PGalligan at rockarch.org>
Date: Thursday, December 2, 2021 at 1:48 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
We’re on version 2.8.0, and we were going to upgrade to 3.1.1 over the weekend.

Can confirm that it’s not causing performance issues, but is inflating the logs like crazy.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Trevor Thornton <trthorn2 at ncsu.edu>
Date: Thursday, December 2, 2021 at 1:46 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
***External*** This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.***

I can confirm that this is a thing, at least it's happening to me as well (we're on v2.8.1 still). It isn't affecting performance from what I can tell, but the lock_version value for the user keeps getting higher (currently over 370000). At some point I shut down AS, reset the lock_version to 0, and restarted, and it just started doing it again.

It doesn't seem to be causing any other problems, but it does fill up the logs, and it's annoying. What version are you on? We're getting ready to upgrade and I was hoping the problem would magically go away when we did.

On Thu, Dec 2, 2021 at 1:11 PM Galligan, Patrick <PGalligan at rockarch.org<mailto:PGalligan at rockarch.org>> wrote:
Peter,

Unfortunately that’s an empty set. It seems like the lock_version is constantly changing for this record. I’m not sure why.

-Patrick

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Peter Heiner <ph448 at cam.ac.uk<mailto:ph448 at cam.ac.uk>>
Date: Thursday, December 2, 2021 at 12:41 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Optimistic locking error
***External*** This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.***

Hi Patrick,

What does
SELECT * FROM `user` WHERE ((`id` = 113) AND (`lock_version` = 1271));
say?

p

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Galligan, Patrick <PGalligan at rockarch.org<mailto:PGalligan at rockarch.org>>
Sent: 02 December 2021 16:57
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Optimistic locking error


Hi all,



I’m trying to diagnose and fix a warning I’m seeing in our AS log files every 12 or 13 seconds:



Got an optimistic locking error when updating user: Attempt to update object did not result in a single row modification (SQL: UPDATE `user` SET `system_mtime` = '2021-12-02 16:52:37', `user_mtime` = '2021-12-02 16:52:37', `lock_version` = 1272 WHERE ((`id` = 113) AND (`lock_version` = 1271)) LIMIT 1)



I can delete the user, but if I remake it with the same username, the warning comes back. If I leave the user open for editing, I get the “This record has been updated by another user. Please refresh the page to access the latest version,” message in the UI.



Any idea how to fix this issue? I’d prefer to be able to keep the username the same. I’m not sure why the system thinks there are two different lock versions associated with the record.



Thanks,

Patrick Galligan

Rockefeller Archive Center
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20211202/24dd15cb/attachment.html>