• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      There are cases that shows Confluence synchronization were hanging and Confluence still think that the process is running fine. Without intervening (restart and database modification) this process, synchronization will not stop.

      This result to multiple issue such as

      • Confluence lock the database table as the directory is on synchronization process
      • No new data being retrieved from LDAP and will continue like this if Confluence administrator does not check the synchronization process
      • Resource locked in memory
      • It is necessary to change the configuration using database UPDATE query on shutdown mode

      By implementing a configurable maximum time of synchronization for example 2 hours or less, we could avoid all the above issue as Confluence will give "Synchronization Failed" message instead of keep it running in the background

            [CONFSERVER-25426] Maximum time of synchronization implementation

            Sen made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3566115 ] New: JAC Suggestion Workflow 3 [ 4332226 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3181446 ] New: JAC Suggestion Workflow 4 [ 3566115 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3037087 ] New: JAC Suggestion Workflow 2 [ 3181446 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2529972 ] New: JAC Suggestion Workflow [ 3037087 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2259623 ] New: Confluence Workflow - Public Facing v4 [ 2529972 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2196274 ] New: Confluence Workflow - Public Facing v3 [ 2259623 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1922439 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2196274 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1757393 ] New: Confluence Workflow - Public Facing v3 [ 1922439 ]
            jonah (Inactive) made changes -
            Description Original: There are cases that shows Confluence synchronization were hanging and Confluence still think that the process is running fine. Without intervening (restart and database modification) this process, synchronization will not stop.

            This result to multiple issue such as

            * Confluence lock the database table as the directory is on synchronization process
            * No new data being retrieved from LDAP and will continue like this if Confluence administrator does not check the synchronization process
            * Resource locked in memory
            * It is necessary to change the configuration using database *UPDATE* query on *shutdown* mode

            By implementing a configurable maximum time of synchronization for example 2 hours or less, we could avoid all the above issue as Confluence will give "Synchronization Failed" message instead of keep it running in the background
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-25426].
              {panel}

            There are cases that shows Confluence synchronization were hanging and Confluence still think that the process is running fine. Without intervening (restart and database modification) this process, synchronization will not stop.

            This result to multiple issue such as

            * Confluence lock the database table as the directory is on synchronization process
            * No new data being retrieved from LDAP and will continue like this if Confluence administrator does not check the synchronization process
            * Resource locked in memory
            * It is necessary to change the configuration using database *UPDATE* query on *shutdown* mode

            By implementing a configurable maximum time of synchronization for example 2 hours or less, we could avoid all the above issue as Confluence will give "Synchronization Failed" message instead of keep it running in the background
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-25426 [ CONFCLOUD-25426 ]

              Unassigned Unassigned
              scahyadiputra Septa Cahyadiputra (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: