Confluence Does Not Start Due to NullPointerException in FelixOsgiContainerManager
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs 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
Confluence will not start. The following error occurs in the atlassian-confluence.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
2009-12-04 18:11:43,303 WARN [main] [sf.hibernate.cache.EhCacheProvider] buildCache Could not find configuration [com.atlassian.confluence.pages.attachments.ImageDetailsDto]; using defaults.
2009-12-04 18:11:45,315 INFO [main] [com.atlassian.confluence.lifecycle] <init> Loading EhCache cache manager
2009-12-04 18:12:04,323 INFO [main] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization completed in 27116 ms
2009-12-04 18:12:04,671 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Initialising the plugin system
2009-12-04 18:12:06,513 ERROR [Felix:Startup] [osgi.container.felix.FelixOsgiContainerManager] doLog Unable to start system bundle.
java.lang.NullPointerException: Specified service reference cannot be null.
at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:320)
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager$BundleRegistration.start(FelixOsgiContainerManager.java:480)
at org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1206)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:630)
at org.apache.felix.framework.Felix$SystemBundleActivator.start(Felix.java:4095)
at org.apache.felix.framework.util.SecureAction$Actions.run(SecureAction.java:1206)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:630)
at org.apache.felix.framework.Felix.init(Felix.java:642)
at org.apache.felix.framework.Felix.start(Felix.java:683)
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager$2.run(FelixOsgiContainerManager.java:269)
at java.lang.Thread.run(Thread.java:619)
Cause
You have not added "grant {permission java.security.AllPermission;}" to the "(TOMCAT)/conf/catalina.policy" file, which is usually there by default.
Resolution
Compare your catalina.policy file to the default to check which ones you have customised. Revert back to the default and check which one of your customised policy settings have denied felix the correct permission that will allow it to start up.
Was this helpful?