App doesn't start (again)

Support
#1

Hi all

I already got problems to launch the app, but we founded some workaround to be able to launch it anyway.
However today it stops working well again.

The message is:
image

The attached catalina.out looks fine
catalina_out.txt (9.9 KB)

I upgraded to the latest version of the plugin (7.2.11) -> no effects
I changed the ports -> no effects

Is there a way to identify what’s wrong and how to fix it ?

Cheers.
O.

#2

Hi,
Attached file doesn’t contain any errors.
Tomcat and CUBA write more log files (catalina.log, localhost.log, app.log and others). Probably the error reason can be in one of those files. In the development environment these files even can be seen in the CUBA project tree, in the “Logs” section.

#3

Hi
I checked these files but didn’t find errors.

catalina.2021-02-01.log (2.7 KB)

localhost.2021-02-01.log (818 Bytes)

localhost_access_log.2021-02-01.txt (72 Bytes)

app.log (9.1 KB)

perfstat.log (3.0 KB)

perfstat-ui.log (360 Bytes)

Any other file to check ?

THanks

#4

Are you sure you are accessing the right Tomcat server?
Because localhost_access_log file should contain entries for all requests received from the browser. And it contains just one line…

If the error started to occur after you’ve changed Tomcat ports, I’d recommend:

  • reset ports in the project to default ones
  • Delete old tomcat from the folder: (project dir)/deploy/tomcat.
  • Execute Gradle task: clean (from CUBA -> Build Tasks menu)
  • And then start application again
#5

Hi.

Yes, the localhost_access_log is the one I get from Cuba Studio. Now it contains 3 lines

127.0.0.1 - - [01/Feb/2021:08:34:57 +0100] "GET /dumbo HTTP/1.1" 302 -
127.0.0.1 - - [01/Feb/2021:08:34:57 +0100] "GET /favicon.ico HTTP/1.1" 404 682
127.0.0.1 - - [01/Feb/2021:08:34:57 +0100] "GET /dumbo/ HTTP/1.1" 200 2276

I tried the recommended steps but the result is unfortunately still the same (error 410).

#6

Probably you have some configuration broken in your project but we don’t know what it is.

Let’s do the following for investigation:

  1. Please present files: app.properties, web-app.properties, build.gradle - cleared from all passwords. Maybe there are some broken settings.

  2. Open your application in Chrome, then press F12 to open Developer Tools.
    Choose Network tab and press F5 again in browser to record what requests are done to the server, maybe there are some errors.

E.g. for a working application it looks like this:

image

#7

F-word !
It worked straight with Chrome. I went back to Firefox, cleaned the cache and it worked again.
This will go directly to my lessons learned handbook.
Sorry for your loss of time but a great thanks: at the end, you found how to fix that.