回复：Re: Artemis backup failover even quorum vote failed because of empty networkhealthcheck

Sorry for late response. Just updated test plan, with 3 master and 1 slave, using static connectors. After 4 node started, the slave become backup of 1 master. Then i use iptables to block outgoing packet on port 61616 at slave side, so it is kind of isolation. 60 seconds later, backup become

Re: Artemis backup failover even quorum vote failed because of empty networkhealthcheck

can you try master? On Thu, May 4, 2017 at 10:53 PM, 怀守昆 wrote: > I'm test Artemis network isolation using quorum vote. > > The backup failover after quorum vote return false. > > I check the code find that in SharedNothingBackupQuorum#decideOnAction, after > test

Artemis backup failover even quorum vote failed because of empty networkhealthcheck

I'm test Artemis network isolation using quorum vote. The backup failover after quorum vote return false. I check the code find that in SharedNothingBackupQuorum#decideOnAction, after test isLiveDown(), networkHealthCheck is also checked. If no network health check url/address configured, it

Re: Artemis production ready?

Just as a FYI: I'm having a last issue that I'm asking help for on the dev-list.. I will start the voting and build the artifacts as soon as I get past that: http://activemq.2283324.n4.nabble.com/DISCUSS-HELP-Help-with-ArtemisFeatureTest-tp4725403.html On Thu, May 4, 2017 at 1:31 PM, Clebert

Re: Artemis production ready?

I will call it 2.1 as it has a few features included. Adding feature means bump it. Only fix is minor. But it's totally compatible with 2.0. On Thu, May 4, 2017 at 1:30 PM Clebert Suconic wrote: > There is a pending PR that I am waiting maven central to sync with

Re: Artemis production ready?

There is a pending PR that I am waiting maven central to sync with the required component. I will start it tonight if everything ok. On Thu, May 4, 2017 at 1:13 PM mtod wrote: > The filtering or routing could be a camel microservice (I have this working > on docker AWS

Re: Artemis production ready?

The filtering or routing could be a camel microservice (I have this working on docker AWS today) or I can work up something using the https://activemq.apache.org/artemis/docs/1.0.0/wildcard-routing.html Our current ActiveMQ uses a Camel content router for managing queue to topics. We setup a

Could not find factory class for resource: META-INF/services/org/apache/activemq/transport/ws

I Integrated activeMQ in jboss in such a way that when I start a project deployed in jboss, activeMQ broker start. I followed a tutorial to integrate activeMQ in jboss. I copied the activemq-rar-5.9.0.rar into the standalone/deployments folder, then I generated the ironjacamar.xml file which I

Re: Activemq web console is not getting up.

What indicates that the exception you quoted is related to the web console? Nothing about that stack trace jumps out at me as being related. On May 3, 2017 10:48 PM, "srinivas.indali" wrote: > Hi All, > > We are upgrading Activemq 5.9 to 5.14.4, messages are getting

Re: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [ws]

I followed a tutorial to integrate activeMQ in jboss. I copied the activemq-rar-5.9.0.rar into the standalone/deployments folder, then I generated the ironjacamar.xml file which I put into the meta-inf folder. The activemq-rar-5.9.0.rar contains a list of jar files. I don't know if should add