geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Baker (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-51) Property hostname-for-clients has an inconsistent behavior between server and locator
Date Fri, 08 Jan 2016 04:40:43 GMT

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

Anthony Baker updated GEODE-51:
-------------------------------
    Fix Version/s: 1.0.0-alpha1

> Property hostname-for-clients has an inconsistent behavior between server and locator
> -------------------------------------------------------------------------------------
>
>                 Key: GEODE-51
>                 URL: https://issues.apache.org/jira/browse/GEODE-51
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: William Markito Oliveira
>            Assignee: William Markito Oliveira
>             Fix For: 1.0.0-alpha1
>
>
> When running Geode on Docker I've discovered a couple problems with hostname-for-clients
property in order to allow external access to the distributed system:
> -  When setting the property for servers through GFSH it seems to be ignored and only
works when using cache.xml.  Note that GFSH setting does work for locators.
> - After specifying hostname-for-clients in cache.xml and attempting to connect using
Java API, although it doesn't throw an UnknownHostException but returns 0 servers in the DS.
 Any operations on the regions return a NoAvailableServersException. 
> Will discuss details with [~dschneider] and confirm the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message