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

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

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.

*Fisheye および Crucible は除く

問題

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

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
....
....

原因

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.

ソリューション

  1. 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. Jira の起動
  5. Re-index Jira again



説明
製品
最終更新日 2021 年 4 月 16 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.