After importing a space, index Item Details are empty, even when there are items in queue to be processed.

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 8.5.0, 9.4.0, 9.4.1, 9.2.4
    • Component/s: Search - Indexing
    • None
    • 1
    • Severity 3 - Minor
    • 0

      Issue Summary

      Index item details at /admin/viewcontentindexqueue.action or /admin/viewchangeindexqueue.action are empty immediately after importing any space.

      Invocation blocked as method is not allowlisted: com.atlassian.confluence.internal.search.tasks.AddDocumentIndexTask#getDescription()

      is also thrown in the atlassian-confluence.log when viewing this admin page.

      Steps to Reproduce

      1. Import any space.
      2. Quickly browse to /admin/viewcontentindexqueue.action or /admin/viewchangeindexqueue.action. If you don't see any number of items Queued for processing, the indexing process may have already run automatically and completed.
      3. Check the section Queued for processing and look for the Item details. The lines are empty.
      4. Check the atlassian-confluence.log for Invocation blocked as method is not allowlisted: com.atlassian.confluence.internal.search.tasks.AddDocumentIndexTask#getDescription().

      Expected Results

      Details about the items in the queue to be processed are expected. The expected result can be found in the screenshot here.

      Actual Results

      The descriptions are missing for Item details, and errors are thrown in the logs:

      2025-05-07 16:30:44,944 WARN [http-nio-6924-exec-7 url: /c924/admin/viewcontentindexqueue.action; user: admin] [velocity] log Invocation blocked as method is not allowlisted: com.atlassian.confluence.internal.search.tasks.AddDocumentIndexTask#getDescription()

      and

      2025-05-07 16:30:54,842 WARN [http-nio-6924-exec-7 url: /admin/viewcontentindexqueue.action; user: admin] [velocity] log Invocation blocked as method is not allowlisted: com.google.common.collect.ImmutableList$SubList#iterator(

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Miranda Rawson (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: