activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Bertram <>
Subject Re: Ping address wasn't reachable
Date Thu, 02 Mar 2017 19:38:26 GMT
It looks to me like it's just the way InetAddress.toString() works.

If there's a bug it may be in the use of, but I'm
no network expert.  If you turn TRACE logging on for org.apache.activemq.artemis.core.server.NetworkHealthCheck
you'll see exactly what it's using when it prints:

  logger.trace("purePing on canonical address " + address.getCanonicalHostName());


----- Original Message -----
From: "Clebert Suconic" <>
Sent: Thursday, March 2, 2017 1:33:30 PM
Subject: Re: Ping address wasn't reachable

It is possible to be a bug on windows...

Can you share your settings? I will take a look.

On Thu, Mar 2, 2017 at 12:29 PM, Harrison Tarr
<> wrote:
> Hello,
> I’m trying to configure HA using Artemis on a Windows machine. My coworker was able
to get the “network-check-list” to work with a simple list of IPs. We are using the same
broker.xml. When I use it, I get an error in the log that says
> “08:56:49,975 | WARN  | ca9-d991d17b6f42 | q.artemis.core.server.NetworkHealthCheck
 206 | ogging.jboss-logging | Ping Address / wasn't reacheable”
> The leading “/” in the IP seems suspicious to me. I have tried using the default
ping command, as well as editing it to be just “ping.” I have also tried with a list or
a single IP. I have also verified that the addresses are reachable from the machine, just
the ping fails. Could there be some parsing error on Windows that is prepending a “/”?
> Regards,
> Harrison Tarr

Clebert Suconic

View raw message