Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-39468

Update SakaiCluster to check on SESSION_ACTIVE rather than waiting for session/locks to timeout

    Details

    • Type: Feature Request
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.9.x
    • Fix Version/s: 10.0
    • Component/s: Kernel
    • Labels:
      None
    • Previous Issue Keys:
      KNL-1006

      Description

      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!

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  k1team KERNEL TEAM (Inactive)
                  Reporter:
                  jonespm Matthew Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code