geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-947) Client log message misleading
Date Fri, 18 Mar 2016 16:28:33 GMT


ASF subversion and git services commented on GEODE-947:

Commit a8d6015b5fd9a66322e81ae91dd947cd9865601c in incubator-geode's branch refs/heads/feature/GEODE-1050
from [~bschuchardt]
[;h=a8d6015 ]

GEODE-947 Client log message misleading

Logging of local-mode or client-mode is now done in GemFireCacheImpl when
the cache is created.  If there is a connection pool or the cache is marked
isClient we want to say it's running in client-mode.  If it's not in client-
mode and the DistributedSystem is not actually configured to be able to
distribute anything we say it's running in local-mode.

I corrected the text of the local-mode message to remove the reference to
multicast since multicast discovery is not supported in Geode.

> Client log message misleading
> -----------------------------
>                 Key: GEODE-947
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Swapnil Bawaskar
>             Fix For: 1.0.0-incubating.M2
> While starting a client, the following message shows up in the logs: 
> {noformat}
> [info 2016/02/09 13:14:15.440 UTC tid=0x1] Running in local mode since mcast-port was
0 and locators was empty.
> {noformat}
> This is confusing to the users, and makes it seem like setting locators in the pool has
had no impact. This message should be changed to something like {{Running in Client Mode}}
when a default Pool has been configured.
> Filed this ticket based on [this thread on stackoverflow|].

This message was sent by Atlassian JIRA

View raw message