[opencms-dev] Why is that exception thrown on a fresh install - The OpenCms setup wizard is still enabled

[Stephan Schrader]

Hi Christoph,

the exception is pretty much normal if you haven't gone through the setup.
Did you do the setup?

Stephan

Am Do., 16. Juli 2020 um 19:00 Uhr schrieb Christoph Kukulies <
kuku at physik.rwth-aachen.de>:

> I did a fresh installation of the opencms_11.0.1.zip,
> downloaded it and deployed it as a ROOT webapp. This had worked all over
> the years. Only this time I would change the frontend server to haproxy
> rather than apache2.
>
> But at the time I’m doing the installation I’m using tomcat 9 (I know 8.5
> is only supported but I don’t think that this matters here)
> I stop tomcat, copy the opencms.war to ROOT.war and start tomcat.
>
> What is bugging me is an exception I get in tomcat/logs/localhost.log:
>
> 16-Jul-2020 18:20:15.693 SEVERE [main]
> org.apache.catalina.core.StandardContext.loadOnStartup Servlet
> [OpenCmsServlet] in web application [] threw load() exception
>  javax.servlet.ServletException: Critical error during OpenCms
> initialization: The OpenCms setup wizard is still enabled.
>         at org.opencms.main.OpenCmsServlet.init(OpenCmsServlet.java:261)
>         at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1124)
>         at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1079)
>         at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:971)
>         at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4829)
>         at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5143)
>         at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>         at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743)
>         at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)
>         at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:703)
>         at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986)
>         at
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1858)
>         at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>         at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>         at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
>         at
> java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
>         at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:772)
>         at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:426)
>         at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1585)
>         at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:308)
>         at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
>         at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:424)
>         at
> org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:367)
>         at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:969)
>         at
> org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:839)
>         at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>         at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1429)
>         at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1419)
>         at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>         at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
>         at
> java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
>         at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:944)
>         at
> org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:261)
>         at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>         at
> org.apache.catalina.core.StandardService.startInternal(StandardService.java:422)
>         at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>         at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:770)
>         at
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
>         at org.apache.catalina.startup.Catalina.start(Catalina.java:682)
>         at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>         at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>         at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:350)
>         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:492)
>
>
>
>
> It’s obvious that the setup wizard is enabled at this time since the setup
> han’t yet taken place, but why does this throw an exception?
>
> Christoph Kukulies
>
>
>
>
>
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20200716/b8e535f6/attachment.htm>