The ResourceConfig instance does not contain any root resource classes Error in Logs
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
Symptoms
The following appears in the atlassian-confluence.log:
2013-03-13 16:48:39,719 http-bio-8080-exec-2 ERROR test 1008x362x1 rb7xtz 0:0:0:0:0:0:0:1 /rest/stp/1.0/license/status [server.impl.application.RootResourceUriRules] The ResourceConfig instance does not contain any root resource classes.
com.atlassian.util.concurrent.LazyReference$InitializationException: com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152)
at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:115)
at com.atlassian.plugin.servlet.DefaultServletModuleManager.getFilter(DefaultServletModuleManager.java:389)
at com.atlassian.plugin.servlet.DefaultServletModuleManager.getFilters(DefaultServletModuleManager.java:213)
...
Caused by: com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.
at com.sun.jersey.server.impl.application.RootResourceUriRules.<init>(RootResourceUriRules.java:99)
at com.sun.jersey.server.impl.application.WebApplicationImpl._initiate(WebApplicationImpl.java:1298)
at com.sun.jersey.server.impl.application.WebApplicationImpl.access$700(WebApplicationImpl.java:169)
at com.sun.jersey.server.impl.application.WebApplicationImpl$13.f(WebApplicationImpl.java:775)
Cause
This problem happens due to a bug in version 3.0.25 of the Support Tools Plugin (STP-233).
Workaround
For Confluence:
- Make a backup of the database.
Run the following query in the Confluence Database:
select plugindataid, pluginkey, filename, lastmoddate from PLUGINDATA where filename like '%stp%';Make sure that the query returns only 1 row. Identify the PLUGINDATAID and run the following query to remove the row:
delete from PLUGINDATA where PLUGINDATAID = <PLUGINID>;Replace <PLUGINID> with the PLUGINDATAID from the first query
- Stop Confluence
- Remove the following folders from the Confluence Home Directory:
bundled-pluginsplugins-cacheplugins-osgi-cacheplugins-temp
- Start Confluence