Internal Tomcat webserver not started up correctly

Discuss all problems you have with Servoy here. It might help to mention the Servoy version and Operating System version you are using

Internal Tomcat webserver not started up correctly

Postby darren » Mon Nov 07, 2022 7:53 pm

As stated in another topic, we're upgrading from 2020.06 to 2022.09. Our two main developers upgraded to 2022.09 and then 2022.09.1 with some issues, but they've been resolved. We then went through the upgrade process for our two JasperReports developers. In addition to working on the JasperReports, they also create simple Servoy forms for passing data to their JasperReports.

For both of the JasperReport devs, we encountered the following error upon starting up Servoy Developer (after installing 2022.09.1):

Internal Tomcat webserver not started up correctly

Please check your startup if you have something else running at http://localhost:8183/


The end result was similar to this issue:
viewtopic.php?f=2&t=23630&hilit=8183

Where the form editor would open the form, but not display anything, which would be expected, since the internal Tomcat wasn't running.

The problem is, there is nothing else running on 8183 in either of these instances.

Then we noticed the 2022.09.2 release and tried installing that for one of the JasperReport devs, and that error disappeared and Developer is functioning well.

Just wondering if 2022.09.2 would have addressed the internal Tomcat error. I've looked at the change notes (https://wiki.servoy.com/display/DOCS/2022.09), but don't know enough about it to determine if any of those fixes would have addressed the error.

Here's the stack trace from the log:

2022-11-04 10:12:16,521 ERROR [Worker-2: Tomcat starter] com.servoy.j2db.util.Debug - Connection refused: connect [ ]
java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect0(Native Method) ~[?:?]
at sun.nio.ch.Net.connect(Unknown Source) ~[?:?]
at sun.nio.ch.Net.connect(Unknown Source) ~[?:?]
at sun.nio.ch.NioSocketImpl.connect(Unknown Source) ~[?:?]
at java.net.Socket.connect(Unknown Source) ~[?:?]
at java.net.Socket.connect(Unknown Source) ~[?:?]
at sun.net.NetworkClient.doConnect(Unknown Source) ~[?:?]
at sun.net.www.http.HttpClient.openServer(Unknown Source) ~[?:?]
at sun.net.www.http.HttpClient.openServer(Unknown Source) ~[?:?]
at sun.net.www.http.HttpClient.<init>(Unknown Source) ~[?:?]
at sun.net.www.http.HttpClient.New(Unknown Source) ~[?:?]
at sun.net.www.http.HttpClient.New(Unknown Source) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) ~[?:?]
at com.servoy.j2db.util.Utils.getURLContent(Utils.java:1605) ~[?:?]
at com.servoy.eclipse.core.tomcat.TomcatStartedListener.started(TomcatStartedListener.java:22) ~[?:?]
at org.apache.tomcat.starter.TomcatStartStop.lambda$0(TomcatStartStop.java:222) ~[?:?]
at java.lang.Iterable.forEach(Unknown Source) ~[?:?]
at java.util.Collections$UnmodifiableCollection.forEach(Unknown Source) ~[?:?]
at org.apache.tomcat.starter.TomcatStartStop.startTomcat(TomcatStartStop.java:222) ~[?:?]
at com.servoy.j2db.server.main.Zav.run(Zav.java:2) ~[?:?]
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) ~[?:?]
darren
 
Posts: 25
Joined: Mon Nov 01, 2021 11:10 pm

Re: Internal Tomcat webserver not started up correctly

Postby darren » Mon Nov 07, 2022 10:42 pm

So, we just tried upgrading the second JasperReports developer's environment from 2020.06 to 2022.09.2, but we're getting the same error.

Internal Tomcat webserver not started up correctly
Please check your startup if you have something else running at http://localhost:8183/

Tried changing \application_server\server\conf\server.xml, so that Tomcat would use port 8191. After that, we're getting the error:

Internal Tomcat webserver not started up correctly
Please check your startup if you have something else running at http://localhost:8191/

We've shut down virus protection and firewalls, closed down other applications. We're on Windows 10, and netstat shows nothing else is on port 8183 (or 8191).

Anyone have any suggestions? Thanks.
darren
 
Posts: 25
Joined: Mon Nov 01, 2021 11:10 pm

Re: Internal Tomcat webserver not started up correctly

Postby jcompagner » Tue Nov 08, 2022 11:33 am

we have never seen this issue. in a 2022.9.x release
so nothing is fixed for this. (also tomcat is not changed at all in this release(s) compared to 06)

That stacktrace doesn't tell me anything that is just our testing code to check if there is a tomcat running on a port that we expect to be running (and nothing is running)

we really need the logs why tomcat is not coming up (so servoy log, workspace log or console:)

maybe you can start the developer once from the command line:

servoy.exe -console

this should open also a console window when starting maybe there we see why it can't start.
Johan Compagner
Servoy
User avatar
jcompagner
 
Posts: 8829
Joined: Tue May 27, 2003 7:26 pm
Location: The Internet

Re: Internal Tomcat webserver not started up correctly

Postby darren » Wed Nov 09, 2022 2:34 am

Thanks for the hint for running servoy.exe from the command prompt. That provided a lot more logging than what was available in servoy.log (The stacktrace I provided above was the only text in the servoy.log file). The additional logging indicated a misconfiguration we had in /application_server/server/conf/server.xml that was the cause of the problem.

The previous version of Tomcat must have allowed the misconfiguration, as it was there for about two years, and didn't cause any problems.

In case you're interested:

Our server.xml customization:

<Context docBase="C:/myapp_data" path="/myapp_data" />

The "myapp_data" folder did not exist at that location.

Nov. 08, 2022 11:40:36 A.M. org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@7c49d281]
at java.base/java.util.concurrent.FutureTask.report(Unknown Source)
at java.base/java.util.concurrent.FutureTask.get(Unknown Source)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:928)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1388)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.base/java.util.concurrent.AbstractExecutorService.submit(Unknown Source)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:921)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:263)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:437)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:934)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.startup.Catalina.start(Catalina.java:772)
at org.apache.tomcat.starter.TomcatStartStop.startTomcat(TomcatStartStop.java:221)
at com.servoy.j2db.server.main.Zav.run(Zav.java:3)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@7c49d281]
at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4885)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5023)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1388)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.base/java.util.concurrent.AbstractExecutorService.submit(Unknown Source)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:921)
... 18 more
Caused by: java.lang.IllegalArgumentException: The main resource set specified [C:\myapp_data] is not valid


thanks again.
darren
 
Posts: 25
Joined: Mon Nov 01, 2021 11:10 pm


Return to Discuss possible Issues and Bugs

Who is online

Users browsing this forum: No registered users and 6 guests

cron