Unable to start Confluence on the browser..
Asked by pritika madkaikar:

When I start up confluence .bat the TomCat server starts up but I get the following on the browser...

System Error

The SystemInformationService could not be retrieved from the container. Therefore very limited information is available in this error report.

The SystemInformationService could not be retrieved due to the following error: java.lang.NullPointerException

Cause

com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException

at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152)

caused by: java.lang.NullPointerException

at com.atlassian.spring.container.ContainerManager.getComponent(ContainerManager.java:33)

Stack Trace: hide

com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException

at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152)

at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:115)

at com.atlassian.confluence.setup.ConfluenceEncodingFilter.getGlobalSettings(ConfluenceEncodingFilter.java:45)

at com.atlassian.confluence.setup.ConfluenceEncodingFilter.getEncodingInternal(ConfluenceEncodingFilter.java:35)

at com.atlassian.confluence.setup.ConfluenceEncodingFilter.getEncoding(ConfluenceEncodingFilter.java:27)

at com.atlassian.core.filters.encoding.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:38)

at com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at com.atlassian.confluence.servlet.FourOhFourErrorLoggingFilter.doFilter(FourOhFourErrorLoggingFilter.java:65)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)

at java.lang.Thread.run(Thread.java:662)

Caused by: java.lang.NullPointerException

at com.atlassian.spring.container.ContainerManager.getComponent(ContainerManager.java:33)

at com.atlassian.confluence.util.LazyComponentReference$Accessor.get(LazyComponentReference.java:44)

at com.atlassian.util.concurrent.Lazy$Strong.create(Lazy.java:88)

at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:326)

at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:146)

... 24 more


Answers:
author: PeterKoczan
body: Hi,

The stack trace itself gives very limited information, you should check atlassian-confluence.log under \<CONFLUENCE_HOME\>/logs directory for more information on the error.

However, based on my experiences this can very likely be caused by your backend database unreachable/ not working properly, but there are other various reasons too.

Nevertheless, please take a look at your logs if it gives more information.

KR,

Peter


author: PeterKoczan
body: Hi,

The stack trace itself gives very limited information, you should check atlassian-confluence.log under \<CONFLUENCE_HOME\>/logs directory for more information on the error.

However, based on my experiences this can very likely be caused by your backend database unreachable/ not working properly, but there are other various reasons too.

Nevertheless, please take a look at your logs if it gives more information.

KR,

Peter


author: PeterKoczan
body: Hi,

The stack trace itself gives very limited information, you should check atlassian-confluence.log under \<CONFLUENCE_HOME\>/logs directory for more information on the error.

However, based on my experiences this can very likely be caused by your backend database unreachable/ not working properly, but there are other various reasons too.

Nevertheless, please take a look at your logs if it gives more information.

KR,

Peter