You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Stuart Harper (JIRA)" <ji...@apache.org> on 2019/04/02 14:55:00 UTC
[jira] [Created] (WW-5028) Dispatcher prints stacktraces directly
to the console
Stuart Harper created WW-5028:
---------------------------------
Summary: Dispatcher prints stacktraces directly to the console
Key: WW-5028
URL: https://issues.apache.org/jira/browse/WW-5028
Project: Struts 2
Issue Type: Bug
Components: Dispatch Filter
Affects Versions: 2.5.18
Reporter: Stuart Harper
After upgrading from Struts 2.3.x to 2.5.x we noticed a stack trace in our logs which was not previously present. The error is actually quite minor and doesn't impact any functionality, the problem is we have no ability to control its presence in our logs do the way the Dispatcher.java prints directly to the console.
This can be seen in class org.apache.struts2.dispatcher.Dispatcher around line 586
Only after the error is printed is a check made on whether to handle it. The exception is then rethrown.
I think it would make more sense to use the logging framework to log exceptions or otherwise give us some control over whether this appears. As it is it's impossible to turn it off.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)