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

RSS whitelist doesn't get persisted in a cluster

XMLWordPrintable

      The whitelist was blank to start with. After adding an entry it said the changes were saved. But when go back to the page the whitelist is empty again. Flushing the "Settings (Persistence)" cache made it work again.
      It seems like the problem is somewhere with the caching of the bandana values.

            [CONFSERVER-15982] RSS whitelist doesn't get persisted in a cluster

            Chris Kiehl added a comment -

            After further investigation I found the following:

            • The data gets correctly persisted to the database and the correct data ends up in the cache
            • The problem only happens if you update the HTML Macros Plugin
            • The com.atlassian.confluence.plugins.macros.html.WhitelistManager.WhitelistData instance returned from the cache will have its class loaded using a different class loader than the updated plugin, therefore the "instanceof" check in com.atlassian.confluence.plugins.macros.html.WhitelistManager.getWhitelistConfig() fails.
            • The problem only happens in a cluster, which is probably due to the replicated cache caching serialized data instead of just object references.

            I don't know yet why it is using a different classloader, as the classloader from the old plugin shouldn't be available any more.

            Chris Kiehl added a comment - After further investigation I found the following: The data gets correctly persisted to the database and the correct data ends up in the cache The problem only happens if you update the HTML Macros Plugin The com.atlassian.confluence.plugins.macros.html.WhitelistManager.WhitelistData instance returned from the cache will have its class loaded using a different class loader than the updated plugin, therefore the "instanceof" check in com.atlassian.confluence.plugins.macros.html.WhitelistManager.getWhitelistConfig() fails. The problem only happens in a cluster, which is probably due to the replicated cache caching serialized data instead of just object references. I don't know yet why it is using a different classloader, as the classloader from the old plugin shouldn't be available any more.

              Unassigned Unassigned
              ckiehl Chris Kiehl
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: