our instance has RB Support - Confluence 5.2.1 installed but am not being offered an update to 5.2.4
here's the exception:
2013-04-04 22:54:32,245 ERROR [main] [atlassian.plugin.manager.PluginEnabler] actualEnable Unable to enable plugin org.swift.confluence.table
com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: org.swift.confluence.table
at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:445)
at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:237)
at com.atlassian.plugin.manager.PluginEnabler.actualEnable(PluginEnabler.java:114)
at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:99)
at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:713)
at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:166)
at com.atlassian.confluence.plugin.ConfluencePluginManager.init(ConfluencePluginManager.java:192)
at com.atlassian.confluence.plugin.PluginFrameworkContextListener.contextInitialized(PluginFrameworkContextListener.java:52)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4704)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
at org.apache.catalina.core.StandardService.start(StandardService.java:525)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.swift.confluence.table-plugin [135]: Unable to resolve 135.0: missing requirement [135.0] package; (&(package=org.randombits.support.confluence)(version>=5.2.4))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1709)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892)
at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:417)
... 22 more
RB Support-Confluence 5.2.4 is not marked as compatible with Confluence 4.x in the marketplace listing. Therefore UPM will not allow it to be manually updated to that level on Confluence 4.x. Table plugin 5.5 includes and requires 5.2.4 and will install it on upgrade. However, if you separately updated RB Support-Confluence back to 5.2.1 it will cause this problem. I am in discussion with Customware on either updating the Marketplace listing for 5.2.4 or providing a workaround release. In the meantime, you have 2 options. You only should do ONE of these.
Sorry for the problem this has caused some customers.
resolved using option 2
confluence now reports 5.2.4 installed, offering 5.2.1 as an update which im ignoring this time ;>
thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Adam,
It looks like the most likely cause of this issue will be corruption of the plugin caches, so I'd like to ask you to try flushing your plugin caches by following the steps below to see if this fixes the issue:
1. Shutdown Confluence
2. Delete the following directories
* <confluence-home>/bundled-plugins folder
* <confluence-home>/plugin-cache folder
* <confluence-home>/plugins-osgi-cache folder
* <confluence-home>/plugins-temp folder
3. Restart Confluence
If this doesn't resolve your issue please open a ticket with Support, remembering to include a copy of your logs, so that we can investigate this issue and advise you how to proceed.
All the best,
John
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.