Jira Re-indexing Fails With Service Proxy Has Been Destroyed Error

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

Jira re-indexing fails with service proxy has been destroyed error. The following appears in the atlassian-jira.log.log:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 2021-04-14 14:00:07,343+0100 JiraTaskExecutionThread-5 INFO xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.j.w.a.admin.index.IndexAdminImpl] Re-indexing started 2021-04-14 14:00:07,343+0100 JiraTaskExecutionThread-5 INFO xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.j.util.index.CompositeIndexLifecycleManager] Reindex All starting... 2021-04-14 14:00:07,343+0100 JiraTaskExecutionThread-5 INFO xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.j.index.ha.DefaultServerIndexRepairService] Pausing DefaultServerIndexRepairService 2021-04-14 14:00:07,343+0100 JiraTaskExecutionThread-5 INFO xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.j.index.ha.NoOpNodeReindexService] [INDEX-REPLAY] No-op:pause 2021-04-14 14:00:07,343+0100 JiraTaskExecutionThread-5 INFO xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.j.index.ha.NoOpNodeReindexService] [INDEX-REPLAY] No-op:resetIndexCount 2021-04-14 14:00:07,343+0100 JiraTaskExecutionThread-5 INFO xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.j.w.a.admin.index.IndexAdminImpl] Re-indexing is 0% complete. Current index: Issue .... .... 2021-04-14 14:00:07,937+0100 IssueIndexer:thread-1 WARN xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.jira.index.AccumulatingResultBuilder] org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed 2021-04-14 14:00:07,937+0100 IssueIndexer:thread-1 WARN xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.jira.index.AccumulatingResultBuilder] org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed 2021-04-14 14:00:07,937+0100 IssueIndexer:thread-1 WARN xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.jira.index.AccumulatingResultBuilder] org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed 2021-04-14 14:00:07,937+0100 IssueIndexer:thread-1 WARN xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.jira.index.AccumulatingResultBuilder] org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed 2021-04-14 14:00:07,937+0100 IssueIndexer:thread-1 WARN xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.jira.index.AccumulatingResultBuilder] org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed 2021-04-14 14:00:07,937+0100 IssueIndexer:thread-1 WARN xxxxxx 840x142576x1 1j6eo7b 142.65.143.41:63670,142.65.159.163 /secure/admin/jira/IndexReIndex!reindex.jspa [c.a.jira.index.AccumulatingResultBuilder] org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed .... ....

Cause

This exception is indicating the accessed OSGi service proxy has been destroyed. Usually, it's thrown when an operation (in this case, it's reindexing) is called on an OSGi service proxy that has been destroyed. One of the root causes of this error is the upgrade of UPM.

Resolution

  1. Stop Jira

  2. Navigate to the plugins directory under <JIRA_HOME> directory.

  3. Delete the .osgi-plugins and .bundled-plugins directories. It is safe to delete the directories themselves as they will be rebuilt when Jira starts.

  4. Start Jira

  5. Re-index Jira again

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.