This installation was working a week ago. In between the server (a VM) has had a hard restart.
This error seems relevant: SEVERE: StandardWrapper.Throwable java.lang.IllegalStateException: No WebApplicationContext found: no ContextLoaderListener registered?
Found this help: https://confluence.atlassian.com/plugins/viewsource/viewpagesrc.action?pageId=284368654 - but there was no trailing slash on the env var.
Logs attached with the error, which happened over and over during startup
14-Sep-2012 17:55:38 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Allocate exception for servlet scmServlet
java.lang.IllegalStateException: No WebApplicationContext found: no ContextLoaderListener registered?
at org.springframework.web.context.support.WebApplicationContextUtils.getRequiredWebApplicationContext(WebApplicationContextUtils.java:90)
at org.springframework.web.context.support.HttpRequestHandlerServlet.init(HttpRequestHandlerServlet.java:56)
at javax.servlet.GenericServlet.init(GenericServlet.java:212)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:809)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
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.Http11AprProcessor.process(Http11AprProcessor.java:864)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1665)
at java.lang.Thread.run(Thread.java:662)
I am having the same problem after a hard restart due to outage. is there a solution ?
This looks tricky ans will probably require some debugging work, best done with our support team. Please contact our support team via our Support Portal. If you have never used our support services before, you'll have to sign up. Let us know the resolution here, if you decide to go that route.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.