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 subversion and git services (JIRA)" <ji...@apache.org> on 2018/02/08 20:43:00 UTC

[jira] [Commented] (GEODE-2569) Unhelpful log message

    [ https://issues.apache.org/jira/browse/GEODE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357535#comment-16357535 ] 

ASF subversion and git services commented on GEODE-2569:
--------------------------------------------------------

Commit 17654b9be859c59a7d26362d4a53851d3515a3ef in geode's branch refs/heads/develop from [~PivotalSarge]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=17654b9 ]

GEODE-2569: Avoid unhelpful log message via a null check. (#1404)

- Since the default for "ack-severe-alert-threshold"
  is zero, there is a code path where the target member
  is null at the point of logging. So check for null.

> Unhelpful log message
> ---------------------
>
>                 Key: GEODE-2569
>                 URL: https://issues.apache.org/jira/browse/GEODE-2569
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server, membership, messaging
>            Reporter: Bruce Schuchardt
>            Assignee: Michael Dodge
>            Priority: Trivial
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I found this in a log file:
> Unable to form a TCP/IP connection to null in over 31 seconds
> Just prior to this the same thread logged this:
> Unable to form a TCP/IP connection to 10.32.109.100(15954)<v6>:48987 in over 31 seconds
> The member mentioned was being removed from the membership view in another thread during this time and nothing malfunctioned, but it isn't useful to print the message with "null" in it.  We should supress that message.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)