On Thu, Mar 2, 2017 at 4:59 PM, Harrison Tarr
wrote:
> I was able to get it to work by changing the ping command to “ping –n %d %s”.
> I’m not sure why it skips the Network.isReachable; the process seems to be
> running as an administrator anyway.
Now, should we make this the default on Windo
I was able to get it to work by changing the ping command to “ping –n %d %s”.
I’m not sure why it skips the Network.isReachable; the process seems to be
running as an administrator anyway.
Thank you very much for your assistance and helping me to identify the problem!
-Harrison
On 3/2/17, 1:4
Notice that the code will first try Network.isReachable(address)
before calling ping...
the fact that you needed the ping, it means that Network.isReachable
wasn't called...
Notice: and this is a very important warning!!!
I have had so restrictions about implementing the networkHealthCheck.
I
On Thu, Mar 2, 2017 at 3:38 PM, Justin Bertram wrote:
> The -c and -t command line switches for the "ping" command mean different
> things between Linux and Windows.
What the? :O
I had tested on Windows when I developed.. I'm not sure if maybe I had
cygwin and it worked because of that? :
" but on Linux it
means "ttl."
Justin
- Original Message -
From: "Harrison Tarr"
To: users@activemq.apache.org
Sent: Thursday, March 2, 2017 2:23:03 PM
Subject: Re: Ping address wasn't reachable
This is the result of setting log lower:
12:17:51,179 | TRA
This is the result of setting log lower:
12:17:51,179 | TRACE | e45-f6f221d82ada |
q.artemis.core.server.NetworkHealthCheck 343 | ogging.jboss-logging | purePing
on canonical address 192.30.252.153
12:17:51,179 | DEBUG | e45-f6f221d82ada |
q.artemis.core.server.NetworkHealthCheck 365 | ogging
rs@activemq.apache.org
Sent: Thursday, March 2, 2017 2:01:48 PM
Subject: Re: Ping address wasn't reachable
I may very well be misunderstanding.
But I think my most pressing issue is that since the NetworkHealthCheck is
failing, my servers are not coming up at all, even when they’re supposed to
I am on 1.5.1.
On 3/2/17, 1:05 PM, "Clebert Suconic" wrote:
Are you using the latest (1.5.3) to debug this?
Just to make sure I would be looking at the same git version I need to look
at.
On Thu, Mar 2, 2017 at 3:01 PM, Harrison Tarr
wrote:
> I may very well be mi
Are you using the latest (1.5.3) to debug this?
Just to make sure I would be looking at the same git version I need to look at.
On Thu, Mar 2, 2017 at 3:01 PM, Harrison Tarr
wrote:
> I may very well be misunderstanding.
> But I think my most pressing issue is that since the NetworkHealthCheck is
I may very well be misunderstanding.
But I think my most pressing issue is that since the NetworkHealthCheck is
failing, my servers are not coming up at all, even when they’re supposed to. I
have tried to start my backup (without the ‘master’ node running) and the
backup does not start Artemis,
Maybe you're misunderstanding how NetworkHealthCheck works?
This is required only to make sure your server will not run in case
you pull out the network cable.
So, if you set the ping Address towards apache.org, your server would
shutdown itself whenever your internet connection drops or the
apa
Please find my broker.xml and backup broker.xml attached. They work when I
comment out the “” but don’t fail-over if I kill the master.
Regards,
Harrison Tarr
On 3/2/17, 12:33 PM, "Clebert Suconic" wrote:
It is possible to be a bug on windows...
Can you share your settings?
'll see exactly
what it's using when it prints:
logger.trace("purePing on canonical address " +
address.getCanonicalHostName());
Justin
- Original Message -
From: "Clebert Suconic"
To: users@activemq.apache.org
Sent: Thursday, March 2, 2017 1:33:30 PM
Subj
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 simp
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
15 matches
Mail list logo
