Issue comment, creation, and mail notifications stop working
プラットフォームについて: Data Center - この記事は、Data Center プラットフォームのアトラシアン製品に適用されます。
このナレッジベース記事は製品の Data Center バージョン用に作成されています。Data Center 固有ではない機能の Data Center ナレッジベースは、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
症状
The creation and of issues, comments, and automatic mail notifications stop functioning correctly in Jira.
Similar errors appear in the: atlassian-jira.log:
2016-02-29 22:19:53,532 Caesium-1-1 ERROR anonymous Mail handler used by Jira Service Desk. Do not modify or delete. 10,300 [c.a.jira.service.ServiceRunner] An error occurred while trying to run service with ID '11000'. This method is not supported in an UnloadableJiraServiceContainer
java.lang.UnsupportedOperationException: This method is not supported in an UnloadableJiraServiceContainer
at com.atlassian.jira.service.UnloadableJiraServiceContainer.setLastRun(UnloadableJiraServiceContainer.java:107)
at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:91)
at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:54)
at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:37)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:453)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:447)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:394)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:279)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:275)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:78)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:70)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:40)
at java.lang.Thread.run(Thread.java:745)
原因
This mostly happens after upgrade and plugins are not present to provide the working classes with their associated services. When the service is then called, it enters an error state and stops the entire services queue from processing. All mail handlers are controlled by services and all errors will need to be addressed. Examples of the services are:
Git Revision Indexing Service : com.xiplink.jira.git.revisions.RevisionIndexService
Service Delay : 3600000ms
Exception getting Service information : java.lang.UnsupportedOperationException: This method is not supported in an UnloadableJiraServiceContainer
Comments from emails : com.atlassian.studio.jira.service.services.file.StudioFileService
Service Delay : 60000ms
Exception getting Service information : java.lang.UnsupportedOperationException: This method is not supported in an UnloadableJiraServiceContainer
Subversion Revision Indexing Service : com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService
Service Delay : 3600000ms
Exception getting Service information : java.lang.UnsupportedOperationException: This method is not supported in an UnloadableJiraServiceContainer
ソリューション
If you have items in the Mail Queue, you should manually flush all items before shutting Jira down
- Navigate to
'Administration' > 'System' > 'Advanced' > 'Services' (tab)
to open the 'Services' page.- OR Keyboard shortcut: 'g' + 'g' + type 'Services'
- Check for any grayed out services
- If there are any grayed services, remove them
- Jira を再起動します。