[
https://issues.apache.org/jira/browse/RIVER-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon IJskes resolved RIVER-389.
--------------------------------
Resolution: Fixed
fixed by river-413 implementation
> TCP Endpoint to check IP address of "localhost"
> -----------------------------------------------
>
> Key: RIVER-389
> URL: https://issues.apache.org/jira/browse/RIVER-389
> Project: River
> Issue Type: Improvement
> Reporter: Tom Hobbs
>
> From the River User mailing list where someone reports a problem starting
> services because of network configuration"
> "This is exactly the kind of complication that makes "getting started" pretty
> painful. Many people would find this to be so odd that they would not even
> ask for help believing that the software had been compiled with a private
> network or that something else was broken in river.
> "We've answered exactly this question with exactly this solution many times
> as I recall. The fact that "security" requires "addresses" to be "correct"
> is one of the no-start issues that will be very prevalent.
> "I believe that we should have the TCP endpoint costructor do a lookup of
> localhost and if it is not 127.0.0.1, log a message, and potentially throw an
> IOException, demanding it be fixed."
> Archive thread can be found here:
> http://mail-archives.apache.org/mod_mbox/incubator-river-user/201101.mbox/%[email protected]%3e
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
