Jira Server or Data Center displays a 404 error when viewing the User Directories administration page
プラットフォームについて: Data Center のみ。 - This article only applies to Atlassian apps on the Data Center プラットフォーム。
この KB は Data Center バージョンの製品用に作成されています。Data Center 固有ではない機能の Data Center KB は、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。 Server* 製品のサポートは 2024 年 2 月 15 日に終了しました。Server 製品を実行している場合は、 アトラシアン Server サポート終了 のお知らせにアクセスして、移行オプションを確認してください。
*Fisheye および Crucible は除く
要約
When navigating toAdministration (⚙) > User Management > User Directories, Jira displays a HTTP 404 error.
診断
Jira logs the error The specified class for ResourceManager (org.apache.velocity.runtime.resource.ResourceManagerImpl) does not implement org.apache.velocity.runtime.resource.ResourceManager; Velocity is not initialized correctly:
2023-08-23 00:00:00,002+0000 https-jsse-nio-443-exec-15 url: /plugins/servlet/embedded-crowd/directories/list; user: <username> INFO <username> 123x45678x9 1234abc 1.2.3.4 /plugins/servlet/embedded-crowd/directories/list [c.a.p.web.springmvc.DispatcherServlet] FrameworkServlet 'Dispatcher Servlet': initialization started
2023-08-23 00:00:00,002+0000 https-jsse-nio-443-exec-15 url: /plugins/servlet/embedded-crowd/directories/list; user: <username> INFO <username> 123x45678x9 1234abc 1.2.3.4 /plugins/servlet/embedded-crowd/directories/list [c.a.p.web.springmvc.DispatcherServlet$1] Refreshing Root WebApplicationContext: startup date [Wed Aug 23 00:00:00 UTC 2023]; parent: NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.crowd.embedded-crowd-admin-plugin, config=osgibundle:/META-INF/spring/*.xml)
2023-08-23 00:00:00,022+0000 https-jsse-nio-443-exec-15 url: /plugins/servlet/embedded-crowd/directories/list; user: <username> ERROR <username> 123x45678x9 1234abc 1.2.3.4 /plugins/servlet/embedded-crowd/directories/list [org.apache.velocity] The specified class for ResourceManager (org.apache.velocity.runtime.resource.ResourceManagerImpl) does not implement org.apache.velocity.runtime.resource.ResourceManager; Velocity is not initialized correctly.
2023-08-23 00:00:00,022+0000 https-jsse-nio-443-exec-15 url: /plugins/servlet/embedded-crowd/directories/list; user: <username> WARN <username> 123x45678x9 1234abc 1.2.3.4 /plugins/servlet/embedded-crowd/directories/list [c.a.p.web.springmvc.DispatcherServlet$1] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'velocityConfig' defined in class path resource [META-INF/spring/web-context.xml]: Invocation of init method failed; nested exception is org.apache.velocity.exception.VelocityException: The specified class for ResourceManager (org.apache.velocity.runtime.resource.ResourceManagerImpl) does not implement org.apache.velocity.runtime.resource.ResourceManager; Velocity is not initialized correctly.
2023-08-23 00:00:00,025+0000 https-jsse-nio-443-exec-15 url: /plugins/servlet/embedded-crowd/directories/list; user: <username> ERROR <username> 123x45678x9 1234abc 1.2.3.4 /plugins/servlet/embedded-crowd/directories/list [c.a.p.web.springmvc.DispatcherServlet] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'velocityConfig' defined in class path resource [META-INF/spring/web-context.xml]: Invocation of init method failed; nested exception is org.apache.velocity.exception.VelocityException: The specified class for ResourceManager (org.apache.velocity.runtime.resource.ResourceManagerImpl) does not implement org.apache.velocity.runtime.resource.ResourceManager; Velocity is not initialized correctly.原因
The exact cause is not known at this time; however, it is believed to relate to a conflict between the Velocity libraries used by Jira's Embedded Crowd plugin (which provides user directory support) and third-party apps. It does not occur immediately after startup, and is suspected to be triggered by a request of some type.
ソリューション
A restart typically resolves this issue; however, if the issue recurs it may be necessary to investigate any third-party apps installed to try to work out which one may be causing the problem. In one such case, updating the Checklist for Jira app to the latest version appeared to resolve the issue.
この内容はお役に立ちましたか?