Uploaded image for project: 'Publishing Transactional'
  1. Publishing Transactional
  2. EEPUBLISH-28

Recurring Problem With Node Locking After Publishing is Causing Closed Sessions

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Neutral
    • 1.1
    • None
    • None
    • Maintenance 22, Maintenance 23, Maintenance 24, Maintenance 25, Maintenance 26, Maintenance 33, Maintenance 34, HL & LD 17, HL & LD 18, HL & LD 19, HL & LD 20, HL & LD 22, HL & LD 23, HL & LD 24, HL & LD 25, HL & LD 26, HL & LD 27, HL & LD 28
    • 8

    Description

      Steps to reproduce

      1. No steps to reproduce - happens randomly on certain environments.

      Expected results

      1. Content is published and unlocked on public instance.

      Actual results

      1. Content publication fails and node remains locked on public instance.

      Workaround

      1. Log in to public instance(s) and remove affected node(s) and republish content.
      2. Use publishing tools to clean mgnlSystem on public instance(s)
        OR
      3. Restart affected public instances

      Development notes

      Investigation ticket, also see tickets linked to PUBLISHING-86.
      Timeboxed to 5sp for investigation

      There is a recurring issue with having nodes locked after publishing. There is something happening where locked nodes are being broken and as a result are closing sessions. 

      Here is an example of what the error is like : 

      2020-08-18 16:50:44,524 WARN  org.apache.jackrabbit.core.lock.LockManagerImpl   : Unable to remove session-scoped lock on node ‘2aaf8f48-bff6-4cb7-a468-f8a95be0c68f-5’: This session has been closed. See the chained exception for a trace of where the session was closed

      Despite attempts at using solutions for regular locked nodes issues, this still persists in some environments. 
       

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            depends upon

            Task - A task that needs to be done. PUBLISHING-99 Move away from JCR node locking

            • Neutral -
            • Closed
            is related to

            Bug - A problem which impairs or prevents the functions of the product. EEPUBLISH-31 Unpublished parent reports node locked

            • Neutral -
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. PUBLISHING-91 Unpublished parent reports node locked

            • Neutral -
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. PUBLISHING-86 Provide an app to clear activation locks

            • Neutral -
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. PUBLISHING-88 Keep track of lock owners with session data

            • Neutral -
            • Closed
            relates to

            Task - A task that needs to be done. PUBLISHING-90 Set default timeout of 5 minutes for locks and increase logging

            • Neutral -
            • Closed
            mentioned in

            Page Loading...

            Page Loading...

            Page Loading...

            Activity

              People

                jsimak Jaroslav Simak
                jnodarse Julian Nodarse
                Nucleus
                Votes:
                3 Vote for this issue
                Watchers:
                17 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD