[
https://issues.apache.org/jira/browse/GEODE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-71:
-------------------------------
Fix Version/s: (was: 1.0.0-incubating)
1.0.0-alpha1
> javadocs for the reason IllegalArgumentException is thrown from addLocator,
> addServer, addPoolLocator, and addPoolServer are not correct
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-71
> URL: https://issues.apache.org/jira/browse/GEODE-71
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Affects Versions: 1.0.0-incubating
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Trivial
> Fix For: 1.0.0-alpha1
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The reason why an IllegalArgumentException is thrown from
> ClientCacheFactory#addPoolLocator,ClientCacheFactory#addPoolServer,PoolFactory#addLocator,
> and PoolFactory#addServer is wrong.
> The javadocs say:
> if host is an unknown host according to InetAddress.getByName(String) or if
> port is outside the valid range of [1..65535] inclusive.
> But they should say:
> if port is outside the valid range of [0..65535] inclusive.
> The product was changed in 7.0 to no longer throw an exception if the host is
> unknown. Instead it waits until the pool is used for an operation. Hopefully
> by that time the host will be know. If it still is not then an exception will
> be thrown.
> Another part of this bug is that when the pool is created with an unknown
> host a fatal log message that just says "Hostname is unknown" is logged.
> Since this is not fatal the message should instead be a warning. The message
> should also explain that the pool will be created with the unknown host.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
