[
https://issues.apache.org/jira/browse/WW-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822357#comment-16822357
]
Hudson commented on WW-5028:
----------------------------
SUCCESS: Integrated in Jenkins build Struts-master-JDK8 #250 (See
[https://builds.apache.org/job/Struts-master-JDK8/250/])
(Amended commit based on feedback) Proposed fix for WW-5028 for the
(yasserzamani: rev f0776aeac6297c849b14921debec4c9cb5653c37)
* (edit) core/src/test/java/org/apache/struts2/dispatcher/DispatcherTest.java
* (edit) core/src/main/java/org/apache/struts2/dispatcher/Dispatcher.java
> 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
> 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 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)
