[
https://issues.apache.org/jira/browse/GEODE-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16567494#comment-16567494
]
ASF subversion and git services commented on GEODE-5157:
--------------------------------------------------------
Commit 555149dc9f6c9c283e3eac96d3656842ee188723 in geode's branch
refs/heads/develop from Helena A. Bales
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=555149d ]
GEODE-5157: use distributedMember as client ID
Changed the client to put stats information in the monitoring region
using the DistributedMember instead of the toString of
DistributedMember. On the server, if that fails, the toString of
DistributedMember is used, for backward compatibility.
This closes #2218
> ClientHealthStats may not be propagated when system has a hostname
> ------------------------------------------------------------------
>
> Key: GEODE-5157
> URL: https://issues.apache.org/jira/browse/GEODE-5157
> Project: Geode
> Issue Type: Bug
> Components: cq, jmx
> Reporter: Jens Deppe
> Assignee: Helena Bales
> Priority: Major
>
> For CQs, the client publishes stats from
> {{ClientStatsManager.publishClientStats}}. Here the client memberId is used
> as a key for putting the stats into an admin region. If the client has a
> valid hostname then the memberId contains the hostname. If there is no valid
> hostname, then the memberId is just the IP address.
> On the server side, clientIDs are determined from {{CacheClientProxy}}
> objects - see {{CacheServerBridge.getUniqueClientIds}}. It appears that these
> IDs are always IP-address based.
> Thus if there is this mismatch then ClientHealthStats are not published
> correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
