Opened 5 years ago

Closed 5 years ago

#1993 closed enhancement (fixed)

Display error messages from startup problems in web client

Reported by: Nicklas Nordborg Owned by: everyone
Priority: minor Milestone: BASE 3.8
Component: web Version:
Keywords: Cc:

Description

If the BASE web client fails to start Tomcat will simply respond with a 404 The requested resource is not available error message.

More detailed information about the startup problems can usually be found in one of the log files. Though it is not always easy to find the correct log file.

It would be nice if some information about the startup problem could be displayed directly in the web client. A typical error is that after a database schema update:

Schema version mismatch: database schema version=131; expected=132; 
Please update the database with the 'updatedb.sh' script before starting BASE.

Change History (1)

comment:1 Changed 5 years ago by Nicklas Nordborg

Resolution: fixed
Status: newclosed

(In [7108]) Fixes #1993: Display error messages from startup problems in web client

StartStopServlet must not throw an exception. This is what causes Tomcat to send a 404 error message.

Turned out that quite a few places expected BASE to be started. This included the error handling pages. Added checks in those places to avoid secondary problems (eg. NullPointerException) from masking the real issue.

Note: See TracTickets for help on using tickets.