struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (WW-5028) Dispatcher prints stacktraces directly to the console
Date Sat, 20 Apr 2019 05:03:00 GMT


Hudson commented on WW-5028:

SUCCESS: Integrated in Jenkins build Struts-master-JDK8 #250 (See [])
(Amended commit based on feedback) Proposed fix for WW-5028 for the (yasserzamani: rev f0776aeac6297c849b14921debec4c9cb5653c37)
* (edit) core/src/test/java/org/apache/struts2/dispatcher/
* (edit) core/src/main/java/org/apache/struts2/dispatcher/

> Dispatcher prints stacktraces directly to the console
> -----------------------------------------------------
>                 Key: WW-5028
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Dispatch Filter
>    Affects Versions: 2.5.18
>            Reporter: Stuart Harper
>            Priority: Minor
>             Fix For: 2.5.21, 2.6
> 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
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

View raw message