Bug 57841 - Change logging defaults to avoid unusable feedback by default
Change logging defaults to avoid unusable feedback by default
Product: Tomcat 7
Classification: Unclassified
Component: Catalina
PC Linux
: P2 normal (vote)
: ---
Assigned To: Tomcat Developers Mailing List
Depends on:
  Show dependency tree
Reported: 2015-04-21 12:00 UTC by krichter
Modified: 2015-04-22 20:12 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description krichter 2015-04-21 12:00:07 UTC
Starting a deployed application can fail with the error message `SCHWERWIEGEND: Error listenerStart` which is unhelpful. Instead provide a usable feedback by default explaining the cause of a severe error. Those should be logged verbosely by default. If very experienced power user want to skip logging of severe/fatal error (even for those it's hard to imagine a cause), they can configure it. By default is should just work.
Comment 1 Christopher Schultz 2015-04-21 14:37:37 UTC
There is usually a "Caused by" section below the "Error listenerStart" line. Is that not the case?
Comment 2 krichter 2015-04-21 19:17:08 UTC
No, it's really only that. I found more detailed error details including an exception stack in `logs/localhost.YYYY-MM-DD.log`. That should be displayed in stdout or referenced there.
Comment 3 Mark Thomas 2015-04-22 20:12:04 UTC
Thanks for the report.

I've been through the StandardContext.startInternal() method and improved all of the error messages. They also now use i18n.

This has been fixed in trunk (9.0.x), 8.0.x/trunk for 8.0.22 onwards and 7.0.x/trunk for 7.0.62 onwards.