[
https://issues.apache.org/jira/browse/GEODE-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275199#comment-17275199
]
ASF subversion and git services commented on GEODE-8873:
--------------------------------------------------------
Commit df07af4c2e27c384b56c78e721c8f8e3e0e61c3f in geode's branch
refs/heads/support/1.12 from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=df07af4 ]
GEODE-8873: Do not log stack trace for Exception in MessageDispatcher
Authored-by: Donal Evans <[email protected]>
(cherry picked from commit 07389149efad9aff18da888b1828639468a884b5)
> MessageDispatcher logs Exception stack trace when stopped
> ---------------------------------------------------------
>
> Key: GEODE-8873
> URL: https://issues.apache.org/jira/browse/GEODE-8873
> Project: Geode
> Issue Type: Improvement
> Components: logging
> Affects Versions: 1.12.0, 1.13.1, 1.14.0
> Reporter: Donal Evans
> Assignee: Donal Evans
> Priority: Major
> Labels: pull-request-available
>
> This message is logged when there are still messages in the queue when the
> cache server thread receives the stop signal or client leaving signal and
> tries to clean up the messages in the queue but encounters an exception. In
> the case of a {{RegionDestroyedException}} or "Broken Pipe" {{IOException}},
> a brief explanation of the cause is logged, but for any other exception
> encountered when attempting to send messages from the queue results in a full
> stack trace being logged, even though the log level is only {{info}}.
> The logging should be changed to only log the exception message, not a full
> stack trace.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
