[
https://issues.apache.org/jira/browse/TUBEMQ-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17115881#comment-17115881
]
viviel edited comment on TUBEMQ-141 at 5/25/20, 9:37 AM:
---------------------------------------------------------
Get the IP feature for the specified network interface name:
It is not easy to get in the construction method of TubeClientConfig. So, I
provide a tool method to get IP through the network interface.
{code:java}
AddressUtils.getIPV4AddressByNetworkInterfaceName()
{code}
was (Author: viviel):
Get the IP feature for the specified network interface name:
It is not easy to get in the construction method of TubeClientConfig. So, I
provide a tool method to get IP through the network interface.
{code:java}
AddressUtils.getIPV4AddressByNetworkInterfaceName ()
{code}
> Remove the requirement to provide localHostIP
> ---------------------------------------------
>
> Key: TUBEMQ-141
> URL: https://issues.apache.org/jira/browse/TUBEMQ-141
> Project: Apache TubeMQ
> Issue Type: Improvement
> Reporter: Guocheng Zhang
> Assignee: viviel
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Attachments: image-2020-05-21-20-54-37-013.png
>
>
> The initial requirement to provide localHostIP during initialization is
> because we have multiple network cards and multiple IPs in our environment.
> The initial implementation is to find the first IP from the specified
> NetworkInterface and report it, but It is found that sometimes the specified
> NetworkInterface is not configured with IP, so, we consider the user is
> required to provide a local IP:
> !image-2020-05-21-20-54-37-013.png!
> After a period of use, the user feedback the API is cumbersome to use. The
> best way is to provide a configurable NetworkInterface API, so if the IP is
> not found, we can change the NetworkInterface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
