You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/08/29 16:58:00 UTC
[jira] [Work logged] (ARTEMIS-2424) Add option to override
InetAddress.isReachable() with purePing()
[ https://issues.apache.org/jira/browse/ARTEMIS-2424?focusedWorklogId=303788&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-303788 ]
ASF GitHub Bot logged work on ARTEMIS-2424:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 29/Aug/19 16:57
Start Date: 29/Aug/19 16:57
Worklog Time Spent: 10m
Work Description: twood2k commented on pull request #2816: ARTEMIS-2424 Network check custom ping priority
URL: https://github.com/apache/activemq-artemis/pull/2816
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 303788)
Remaining Estimate: 0h
Time Spent: 10m
> Add option to override InetAddress.isReachable() with purePing()
> ----------------------------------------------------------------
>
> Key: ARTEMIS-2424
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2424
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Thomas Wood
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This might be a bug.... not sure what the original intent was.
> Documentation states that a custom ping command can be configured, but...
> the NetworkHealthCheck:check() function will never use a custom ping command unless InetAddress.isReachable fails. it would be nice to add an option to override this behavior or refactor to make the custom ping command a priority.
> thanks!
--
This message was sent by Atlassian Jira
(v8.3.2#803003)