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 2022/06/15 23:16:00 UTC

[jira] [Updated] (GEODE-10384) Improve logging with stack trace for gateway senders

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

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

> Improve logging with stack trace for gateway senders
> ----------------------------------------------------
>
>                 Key: GEODE-10384
>                 URL: https://issues.apache.org/jira/browse/GEODE-10384
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: Jianxia Chen
>            Priority: Major
>              Labels: pull-request-available
>
> In ConcurrentSerialGatewaySenderEventProcessor.stopProcessing, the log does not print out the stack trace, making it hard figure out the root cause:
> {code:java}
> logger.warn("GatewaySender {} caught exception while stopping: {}",
>     new Object[] {sender, e.getCause()}); {code}
> For example, the log would be something without stack trace:
> {code:java}
> [warning 2022/06/14 20:41:17.412 PDT peergemfire_2_2_host1_20886 <vm_9_thr_32_peer_2_2_host1_20886> tid=0x1cc] GatewaySender SerialGatewaySender{id=sender_ds_2_to_ds_1,remoteDsId=1,isRunning =false,isPrimary =true} caught exception while stopping: java.lang.NullPointerException {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)