This might have been one already fixed by
KNL-497, but we still get users who closed the browser while editing announcements who seem to get locked out for an extended period of time.
The exception is being thrown from BaseMessageService when either editChannel or editMessage is called.
// ignore the cache - get the channel with a lock from the info store
MessageChannelEdit edit = m_storage.editChannel(ref);
if (edit == null) throw new InUseException(ref);
The locks are in the SAKAI_LOCKS table
return "insert into SAKAI_LOCKS (TABLE_NAME,RECORD_ID,LOCK_TIME,USAGE_SESSION_ID) values (?, ?, ?, ?)";
Though I still think these locks are only cleaned up on the SakaiClusterService maintenance thread?
If this was fixed, please mark as "Not an Issue" but if anyone else has any advice on how/where to fix it would be useful! Thanks!