Confluence error on upgrading from 7.4.11 to 7.13.7
Asked by m.cecere:

During upgrade some errors appear in the catalina.out and atlassian-confluence.log logs and section **Manage Apps** won't work:![upm_confluence.PNG](/t5/image/serverpage/image-id/203732iA1C44124162704F3/image-size/large?v=v2&px=999 "upm_confluence.PNG")  

<br />

<br />

**catalina.out**   
com.sun.jersey.core.spi.component.ProviderFactory.__getComponentProvider The provider class, class com.sun.jersey.json.impl.provider.entity.JSONObjectProvider, could not be instantiated. Processing will continue but the class will not be utilized  
java.lang.IllegalAccessException: class com.sun.jersey.core.spi.component.ComponentConstructor cannot access a member of class com.sun.jersey.json.impl.provider.entity.JSONObjectProvider with modifiers ""  
at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)  
at java.base/jdk.internal.reflect.Reflection.ensureMemberAccess(Reflection.java:99)  
at java.base/java.lang.Class.newInstance(Class.java:579)  
........  

**atlassian-confluence.log**   
io.atlassian.util.concurrent.LazyReference$InitializationException: com.sun.jersey.api.container.ContainerException: No WebApplication provider is present  
at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:156)  
at io.atlassian.util.concurrent.LazyReference.get(LazyReference.java:116)  
at com.atlassian.plugin.servlet.DefaultServletModuleManager.getInstance(DefaultServletModuleManager.java:431)  
at com.atlassian.plugin.servlet.DefaultServletModuleManager.getFilter(DefaultServletModuleManager.java:424)  
at com.atlassian.plugin.servlet.DefaultServletModuleManager.getFilters(DefaultServletModuleManager.java:289)  
at com.atlassian.plugins.rest.module.servlet.DefaultRestServletModuleManager.getFilters(DefaultRestServletModuleManager.java:125)  
at com.atlassian.plugin.servlet.filter.ServletFilterModuleContainerFilter.doFilter(ServletFilterModuleContainerFilter.java:54)  
at com.atlassian.plugin.servlet.filter.ServletFilterModuleContainerFilter.doFilter(ServletFilterModuleContainerFilter.java:44)  
at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:62)  
at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:37)  
at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.lambda$doFilter$0(DelegatingPluginFilter.java:57)  
at com.atlassian.plugins.rest.module.servlet.RestServletUtilsUpdaterFilter.doFilterInternal(RestServletUtilsUpdaterFilter.java:23)  
at com.atlassian.plugins.rest.module.servlet.RestServletUtilsUpdaterFilter.doFilter(RestServletUtilsUpdaterFilter.java:35)  
at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:62)  
at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:37)  
at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.lambda$doFilter$0(DelegatingPluginFilter.java:57)  
at com.atlassian.applinks.core.rest.context.ContextFilter.doFilter(ContextFilter.java:24)  
....................  

<br />

<br />


Answers:
author: Benjamin
body: Hi [@m.cecere](/t5/user/viewprofilepage/user-id/4349473) ,

I'm assuming that when you mean it doesn't work, you mean that your apps are not populating on the page.

Try these following steps:

* Clear your cache and see if you still have the same issue.
* [Clear your plugin cache - clear confluence plugin cache](https://confluence.atlassian.com/confkb/how-to-clear-confluence-plugins-cache-297664846.html)

Thanks,

Ben

comments: author: m.cecere
body: Hi Ben,  
I mean I cannot see the "Upload new app" button and I cannot see two custom plugins installed.  
I cleared the cache but nothing changed.


author: Benjamin
body: Hi [@m.cecere](/t5/user/viewprofilepage/user-id/4349473) ,

Did you follow the 2nd bullet point as well?

If you still seeing issue after the restart, then would suggest to contact Atlassian Support.

Thanks,

Ben


author: m.cecere
body: Yes, I follow both steps but nothing changed. Every call that Confluence makes to pages, spaces, custom apps ecc... goes to 404.


author: Benjamin
body: That's strange. Recommend retracing all your steps you did for the upgrade. Make sure nothing was accidentally miss. Keep in mind that when you upgrade, customize files do not get carried over.

If still have issue, would suggest contact Atlassian Support.

thanks,

Ben


Tags: confluence-server

server

upgrade