Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-56352

Improve Data Center license system

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 5.6
    • Data Center - Core
    • None

      Currently Confluence stores the license details in the confluence.cfg.xml file, which is stored locally on each node.

      When ever a license is installed on a node, the license details need to be distributed to each of the other nodes to be installed and stored in the confluence.cfg.xml file.

      Prior to Confluence 5.6, license changes were not propagated across nodes (a bug). In Confluence 5.6, license changes are propagated to other nodes using the cluster event InternalLicenceUpdatedEvent.

      The problem is that if a node is not active when a license is installed, it will not receive the cluster event InternalLicenceUpdatedEvent.

      Workaround

      • update the license key manually on the newly joined nodes which license key hasn't updated
      • Alternatively, we strongly recommend you update the respective AMI every time a new license key is applied to the active node within the existing cluster.

          Form Name

            [CONFSERVER-56352] Improve Data Center license system

            Katherine Yabut made changes -
            Workflow Original: JAC Bug Workflow v3 [ 2889833 ] New: CONFSERVER Bug Workflow v4 [ 2982182 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2775982 ] New: JAC Bug Workflow v3 [ 2889833 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Usman Khalid (Inactive) made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Needs Triage [ 10030 ] New: Resolved [ 5 ]
            Usman Khalid (Inactive) made changes -
            Link New: This issue duplicates CONFSERVER-56375 [ CONFSERVER-56375 ]
            Usman Khalid (Inactive) made changes -
            Link Original: This issue is cloned from CONFSRVDEV-373 [ CONFSRVDEV-373 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Owen made changes -
            Workflow Original: JAC Bug Workflow [ 2773772 ] New: JAC Bug Workflow v2 [ 2775982 ]
            Ivan Tse made changes -
            Link New: This issue is cloned from CONFSRVDEV-373 [ CONFSRVDEV-373 ]
            Ivan Tse made changes -
            Description New: Currently Confluence stores the license details in the {{confluence.cfg.xml}} file, which is stored locally on each node.

            When ever a license is installed on a node, the license details need to be distributed to each of the other nodes to be installed and stored in the {{confluence.cfg.xml}} file.

            Prior to Confluence 5.6, license changes were not propagated across nodes (a bug). In Confluence 5.6, license changes are propagated to other nodes using the cluster event {{InternalLicenceUpdatedEvent}}.

            The problem is that if a node is not active when a license is installed, it will not receive the cluster event {{InternalLicenceUpdatedEvent}}.

            *Workaround*
            * update the license key manually on the newly joined nodes which license key hasn't updated
            * Alternatively, we strongly recommend you update the respective AMI every time a new license key is applied to the active node within the existing cluster.
            Ivan Tse created issue -

              Unassigned Unassigned
              itse Ivan Tse
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: