Unable to Start Confluence Due to Malfunctioning Plugin

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

Confluence is unable to start. The following appears in the atlassian-confluence.log:

2010-04-20 21:46:44,023 ERROR [main] [atlassian.confluence.event.ConfluenceEventManager] publishEvent An exception was encountered while processing the event:
com.atlassian.confluence.event.events.admin.ConfluenceReadyEvent[source=com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager@49a1c5]
com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to install bundle
	at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.installBundle(FelixOsgiContainerManager.java:358)
...
Caused by: org.osgi.framework.BundleException: Could not create bundle object.
	at org.apache.felix.framework.Felix.installBundle(Felix.java:2370)
	at org.apache.felix.framework.Felix.installBundle(Felix.java:2227)
...
Caused by: java.lang.NumberFormatException: For input string: "${project"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
	at java.lang.Integer.parseInt(Integer.java:447)
...
  • A plugin was recently installed in Confluence.

Cause

Upon each restart, Confluence loads installed plugins stored in the database. In this case, a plugin is malfunctioning or incompatible with the Confluence version, preventing Confluence from starting up.

Resolution

Remove the offending plugin from the database. See How to manually remove malfunctioning add-ons.

Still having problems?
If the offending plugin is hard to identify, grab a list of installed plugins from the database for backup reference:

SELECT plugindataid, pluginkey, filename, lastmoddate FROM plugindata ORDER BY lastmoddate DESC;

Then, truncate the table and proceed to reinstall the plugins one by one until the issue returns.

Last modified on Nov 2, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.