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

Confluence Mail Archiving flooding the logs with CQL errors

    XMLWordPrintable

Details

    Description

      Summary

      The Confluence Mail Archiving add-on seems to be flooding the atlassian-confluence.log, related to CQL.

      Steps to Reproduce

      1. Enable the Confluence Mail Archiving add-on
      2. Check the atlassian-confluence.log for stacktraces

      Expected Results

      No stack traces in the logs

      Actual Results

      The below exception is thrown in the xxxxxxx.log file:

      2016-02-09 16:23:44,421 ERROR [http-nio-8090-exec-1] [plugins.cql.impl.SearchTypeManager] getCustomContentTypes A plugin installed content type caused an error for the CQL plugin, removing custom content
      type from CQL handled types : com.atlassian.confluence.plugins.confluence-mail-archiving:mail
       -- referer: http://localhost:8090/ | url: /rest/experimental/search | userName: admin
      java.lang.UnsupportedOperationException
              at com.atlassian.confluence.security.delegate.AbstractPermissionsDelegate.canView(AbstractPermissionsDelegate.java:27)
              at com.atlassian.confluence.plugins.cql.impl.SearchTypeManager.getCustomContentTypes(SearchTypeManager.java:127)
              at com.atlassian.confluence.plugins.cql.impl.SearchTypeManager.getContentTypes(SearchTypeManager.java:102)
              at com.atlassian.confluence.plugins.cql.impl.SearchTypeManager.getTypes(SearchTypeManager.java:193)
              at com.atlassian.confluence.plugins.cql.impl.SearchTypeManager.hasType(SearchTypeManager.java:198)
              at com.atlassian.confluence.plugins.cql.fields.ContentTypeFieldHandler.checkTypeExists(ContentTypeFieldHandler.java:146)
              at com.atlassian.confluence.plugins.cql.fields.ContentTypeFieldHandler.lambda$new$6(ContentTypeFieldHandler.java:104)
              at com.atlassian.confluence.plugins.cql.fields.ContentTypeFieldHandler$$Lambda$98/1921253214.apply(Unknown Source)
              at com.google.common.collect.Iterators$8.next(Iterators.java:812)
              at com.google.common.collect.Iterables$3.next(Iterables.java:508)
              at com.google.common.collect.Iterables$3.next(Iterables.java:501)
              at com.google.common.collect.Iterators$5.hasNext(Iterators.java:544)
              at com.atlassian.fugue.Iterables$Memoizer.nextNode(Iterables.java:614)
              at com.atlassian.fugue.Iterables$Memoizer.<init>(Iterables.java:606)
              at com.atlassian.fugue.Iterables.memoize(Iterables.java:301)
      

      Workaround

      The workaround is to disable the add-on if it is not in use. If it is in use, there is no workaround.

      Attachments

        Issue Links

          Activity

            People

              ciacullo Christian Iacullo (Inactive)
              mrawson Miranda Rawson
              Votes:
              4 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: