You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/01/28 17:19:00 UTC

[jira] [Updated] (GEODE-8873) MessageDispatcher logs Exception stack trace when stopped

     [ https://issues.apache.org/jira/browse/GEODE-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated GEODE-8873:
----------------------------------
    Labels: pull-request-available  (was: )

> 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)