Details

    • ACT Numbers:

      17169

      Description

      If an ldap synch is aborted in the middle of the synch (e.g. by stopping Alfresco), the synch will refuse to run again for the next 24 hours, and will throw in the log:
      [org.alfresco.repo.security.sync.ChainingUserRegistrySynchronizer] User registry synchronization already running in another thread. Synchronize aborted

      Steps to reproduce:

      • Configure Alfresco to perform an LDAP synch - set it run e.g. every 5 minutes
      • Stop Alfresco whilst in the middle of the synch.
      • Restart Alfresco
      • Wait until the next run should kick off

      – Expected behaviour

      • synch performs as normal
        • Observed behaviour
      • above error is thrown in log.

      Analysis:
      ChainingUserRegistrySynchronizer gets a lock for 24 hours. Can we reduce this?
      /** The maximum time this lock will be held for (1 day). */
      private static final long LOCK_TTL = 1000 * 60 * 60 * 24;

      Workaround:
      Remove the lock from the DB:
      To find out which row to remove from the alf_lock table:
      select * from alf_lock where shared_resource_id = (select id from alf_lock_resource where qname_localname = 'chaininguserregistrysynchronizer');

        Activity

        Hide
        Steve Rigby added a comment -

        Review for inclusion in 3.3E or for future

        Show
        Steve Rigby added a comment - Review for inclusion in 3.3E or for future
        Hide
        dward added a comment -

        Could you please recommend the best way of ensuring this lock gets invalidated? Perhaps we should just clear it on start up?

        Show
        dward added a comment - Could you please recommend the best way of ensuring this lock gets invalidated? Perhaps we should just clear it on start up?
        Hide
        dward added a comment -

        Now the lock is refreshed at 1 minute intervals and never persists for more than 2 minutes.

        Show
        dward added a comment - Now the lock is refreshed at 1 minute intervals and never persists for more than 2 minutes.
        Hide
        Alfresco QA Team added a comment -

        Successfully validated at Alfresco 3.3.2 b 138 - Stack 1 RHEL 5.1 x64, Tomcat 6.0.26, Mysql 5.1.39, JDK 6u18 x64, Alfresco + OpenLDAP, Windows XP, FF 3

        Show
        Alfresco QA Team added a comment - Successfully validated at Alfresco 3.3.2 b 138 - Stack 1 RHEL 5.1 x64, Tomcat 6.0.26, Mysql 5.1.39, JDK 6u18 x64, Alfresco + OpenLDAP, Windows XP, FF 3

          People

          • Assignee:
            Closed Bugs
            Reporter:
            Andrew Hunt
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: