Confluence Menus Do Not Work, or Confluence Fails to Start when Running in the Same Application Server as JIRA 4.0, 4.0.1 or Crowd 2.0.x
Confluence starts up but, amongst other things, the menus and the editor don't work. The log file will show the following stacktrace:
2009-12-04 11:29:34,696 FelixStartLevel ERROR [extender.internal.activator.ContextLoaderListener] Unable to process extender configuration org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from OSGi resource[bundle://3.0:0/META-INF/spring/extender/spring-event-bridge.xml|bnd.id=3|bnd.sym=org.springframework.osgi.extender]; nested exception is java.io.IOException: No framework context found at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:349) ... Caused by: java.io.IOException: No framework context found at org.apache.felix.framework.URLHandlersBundleStreamHandler.openConnection(URLHandlersBundleStreamHandler.java:69)
This is caused by JIRA 4.0.x or Crowd 2.0.x and Confluence 3.1.x running in the same Java Virtual Machine (ie. Application Server). It's due to the fact that Confluence 3.1 uses a newer version of Atlassian Plugins which brings a newer version of Apache Felix (2.0.1) with it. This version of Felix is not compatible with the the version of Felix JIRA 4.0 or Crowd 2.0.x provides (1.2.1) if both versions run in the same Java VM.
Please ensure that you are not running multiple Atlassian applications in a single Tomcat container. See this FAQ for more information.
See Unable to Start JIRA when Running with Confluence or Crowd in the Same Application Server Container for a solution.
Issues with browser caching
Several users reported that they had to clear their browser cache and reload the web page. If downloading the JAR doesn't fix the issue then please try clearing the browser cache.
Was this helpful?Yes Provide feedback about this article