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

Stephan Schrader zstephanz at gmail.com
Fri Jul 17 09:35:42 CEST 2020


Am Fr., 17. Juli 2020 um 09:10 Uhr schrieb Christoph Kukulies <
kuku at physik.rwth-aachen.de>:

> Hi Stephan,
>
> thanks. At this point I haven't gone through the setup. I haven't even
> invoked any piece of OpenCms at this point in time. I just started the
> container with the webapp (OpenCms, ROOT in this case)
>
> Even if you say this is normal - I understand the textual notification "The
> OpenCms setup wizard is still enabled." - I totally agree with that but
> on the other hand I totally disagree that it has to be accompanied with an
> ugly backtrace.
>
> It doesn't have to be that the first start of OpenCms is producing a java
> exeption with a backtrace. I'm with OpenCms for 20 years now :)
> and  I believe this has been the case all the time, but it's time to
> change that.
>
> As soon as I have time I will change that in the OpenCms source and supply
> a patch that suppresses this exception bomb
> and answers gently.
>

I'm totally with you! Go for it.

Another interesting feature in relation to setup is to have the AutoSetup
start automatic, if the wizard ist enabled and a configuration file is
provided somewhere.
https://documentation.opencms.org/opencms-documentation/server-installation/installing-opencms/the-setup-script/


>
> When you want to inspect the logs to see if everything has started fine
> there shouldn’t be the neccessity to wad through a long backtrace to
> finally find that
> little text message.
>

;)

Stephan


>
>> Christoph
>
> Am 16.07.2020 um 20:42 schrieb Stephan Schrader <zstephanz at gmail.com>:
>
> 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)
>>
>>
> _______________________________________________
> 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/20200717/333c5332/attachment.htm>


More information about the opencms-dev mailing list