Jira Server or Data Center displays a 404 error when viewing the User Directories administration page
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
Summary
When navigating toAdministration (⚙) > User Management > User Directories, Jira displays a HTTP 404 error.
Diagnosis
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:
1
2
3
4
5
6
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.Cause
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.
Solution
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.
Was this helpful?