Master-Slave with Network of Brokers ActiveMQ Classic 5.18.4

I am setting up four ActiveMQ brokers on two separate machines. Master A Machine 1 Slave B on Machine 1 Slave A on Machine 2 Master B on Machine 2 Master C Machine 1 Slave D on Machine 1 Slave C on Machine 2 Master D on Machine 2 All of the brokers are running and there are no issues. The net

Re: Trouble with Replication HA Master/Slave config performing failback

ancel the transactions and connect to another application server and retry them there, which is comparatively fairly quick. Thanks, Paul From: Justin Bertram Date: Friday, February 2, 2024 at 2:34 PM To: users@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave c

Re: Trouble with Replication HA Master/Slave config performing failback

onsistent state of the system as it does on > startup. > > Thanks, > Paul. > > From: Justin Bertram > Date: Monday, January 22, 2024 at 9:26 AM > To: users@activemq.apache.org > Subject: Re: Trouble with Replication HA Master/Slave config performing > failback > Looking at the code everything seems to be in order. Can you work up a > test-case to reproduce the issue you're seeing? Slap it on GitHub, and I'll > take a look. > > > Justin >

Re: Trouble with Replication HA Master/Slave config performing failback

application can derive a consistent state of the system as it does on startup. Thanks, Paul. From: Justin Bertram Date: Monday, January 22, 2024 at 9:26 AM To: users@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave config performing failback Looking at the code everything seems

Re: Trouble with Replication HA Master/Slave config performing failback

I’ll put together a test case. Thanks, Paul From: Justin Bertram Date: Monday, January 22, 2024 at 9:26 AM To: users@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave config performing failback Looking at the code everything seems to be in order. Can you work up a test

Re: Trouble with Replication HA Master/Slave config performing failback

Looking at the code everything seems to be in order. Can you work up a test-case to reproduce the issue you're seeing? Slap it on GitHub, and I'll take a look. Justin

Re: Trouble with Replication HA Master/Slave config performing failback

We are using QoS = 1. Paul From: Justin Bertram Date: Monday, January 22, 2024 at 9:09 AM To: users@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave config performing failback What QoS are you using to send the message(s)? Messages sent with QoS 0 are non-durable and

Re: Trouble with Replication HA Master/Slave config performing failback

message does not > contain the last will message). > > Thanks, > Paul > > [1]: > https://activemq.apache.org/components/artemis/documentation/latest/ha.html#ha-policies > > From: Justin Bertram > Date: Friday, January 19, 2024 at 11:47 AM > To: users@activemq.apac

Re: Trouble with Replication HA Master/Slave config performing failback

@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave config performing failback > So even though the persistent data will be stored pod-local... If you disable persistence on the broker then no data will be persisted on the local pod. > ...enabling persistence has the knock-on eff

Re: Trouble with Replication HA Master/Slave config performing failback

ibe > > -- > *From:* John Lilley > *Sent:* Friday, January 19, 2024 10:24:39 PM > *To:* users@activemq.apache.org > *Subject:* RE: Trouble with Replication HA Master/Slave config performing > failback > > > Hi Paul, > > > > Thanks for all of thi

Re: Trouble with Replication HA Master/Slave config performing failback

Thanks Justin! I will make that change and give it a try. Paul From: Justin Bertram Date: Monday, January 15, 2024 at 10:56 PM To: users@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave config performing failback In the replication case you still need a PV in K8s, but

Re: Trouble with Replication HA Master/Slave config performing failback

02481 > > lino.pere...@redpointglobal.com > > -Original Message- > From: Justin Bertram > Sent: Friday, January 12, 2024 4:53 PM > To: users@activemq.apache.org > Subject: Re: Trouble with Replication HA Master/Slave config performing > failback > > *** [Ca

Re: Trouble with Replication HA Master/Slave config performing failback

ray-dvs-mqtt-ss-0-cray-dvs-mqtt-hdls-svc-dvs-svc-cluster-local) Thanks, Paul From: Justin Bertram Date: Friday, January 12, 2024 at 3:38 PM To: users@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave config performing failback > Is it possible to use jgroups instead of U

Re: Trouble with Replication HA Master/Slave config performing failback

org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector] > Connector NettyConnector > [host=cray-dvs-mqtt-ss-0.cray-dvs-mqtt-hdls-svc.dvs.svc.cluster.local, > port=61616, httpEnabled=false, httpUpgradeEnabled=false, useServlet=false, > servletPath=/messaging/ActiveMQServlet, s

Re: Trouble with Replication HA Master/Slave config performing failback

tram Date: Wednesday, December 13, 2023 at 3:23 PM To: users@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave config performing failback ActiveMQ Artemis ships with an example in the examples/features/ha/replicated-failback directory that demonstrates how this work

Re: Trouble with Replication HA Master/Slave config performing failback

From: Justin Bertram Date: Wednesday, December 13, 2023 at 3:23 PM To: users@activemq.apache.org Subject: Re: Trouble with Replication HA Master/Slave config performing failback ActiveMQ Artemis ships with an example in the examples/features/ha/replicated-failback directory that demonstrates how this

Re: Trouble with Replication HA Master/Slave config performing failback

ActiveMQ Artemis ships with an example in the examples/features/ha/replicated-failback directory that demonstrates how this works. I ran this example and it worked fine. I also started up the brokers manually and triggered failover and failback. Again, everything worked fine. My only guess is that

Trouble with Replication HA Master/Slave config performing failback

Hi, I am having an issue with failback to the master broker. I start the master broker then the slave broker. I see the replication from the master to the slave happen. I stop the master/active broker and a failover happens to the slave as expected. When the master is started a failback to i

Re: lock file modification issue in Master/Slave mode with Shared file locker

Kubernetes Thanks, Matt Pavlovich > On Dec 5, 2023, at 3:05 PM, HOUNGBE, Fabrice (MTL) > wrote: > > Hi, > We have a Master/Slave config with Classic ActiveMQ flavor. Our 2 servers > share the same KahaDB (NFS/SMB). > Since we upgrade the OS from windows server 2016 t

lock file modification issue in Master/Slave mode with Shared file locker

Hi, We have a Master/Slave config with Classic ActiveMQ flavor. Our 2 servers share the same KahaDB (NFS/SMB). Since we upgrade the OS from windows server 2016 to Win Server 2019, We noticed an error in log file like below: === Lock file \\share_location\lock, locked at Tue Dec 05 15:52:32 EST

RE: Kubernetes Artemis Master Slave Issue

(ActiveMQThreadFactory.java:118) [artemis-commons-2.19.1.jar:2.19.1] Thanks, Shivang -Original Message- From: Justin Bertram Sent: Monday, July 24, 2023 10:18 PM To: users@activemq.apache.org Subject: Re: Kubernetes Artemis Master Slave Issue As far as I can tell no error is actually being reported here

Re: Kubernetes Artemis Master Slave Issue

te: > Hi Team, > > > > I have requirement to create Artemis master slave shared storage cluster > using Postgres database in Kubernetes. Here is > > > > *Master broker.xml* > > > > > > > > > > >xmlns:xsi=http://www.w3.o

Kubernetes Artemis Master Slave Issue

Hi Team, I have requirement to create Artemis master slave shared storage cluster using Postgres database in Kubernetes. Here is *Master broker.xml* http://www.w3.org/2001/XMLSchema-instance xmlns:xi=http://www.w3.org/2001/XInclude xsi:schemaLocation

Re: When I used JDBC to connect MySQL to build a 2-node master-slave, I found that the table ACTIVEMQ in the database_ LOCK No data

发件人: "users" ; > 发送时间: 2023年6月27日(星期二) 凌晨3:21 > 收件人: "users@activemq.apache.org"; > 主题: Re: When I used JDBC to connect MySQL to build a 2-node master-slave, I > found that the table ACTIVEMQ in the database_ LOCK No data > > Hi- > > 5.15.x is no longer a

?????? When I used JDBC to connect MySQL to build a 2-node master-slave, I found that the table ACTIVEMQ in the database_ LOCK No data

Same as using the latest version, there is no data in the ACTIVEMQ_LOCK. Is the configuration file missing content ??o.-- 1169114...@qq.com   --  -- ??:

Re: When I used JDBC to connect MySQL to build a 2-node master-slave, I found that the table ACTIVEMQ in the database_ LOCK No data

NVALID> wrote: > > Hello >    When I used JDBC to connect MySQL to build a 2-node > master-slave, I found that the table ACTIVEMQ in the database_ LOCK No > data，5.15.9 version > > > ---activemq.log  2node the log is same- > > 2023-

RE: ActiveMQ 5.16.x Master/Slave topology question

users@activemq.apache.org Subject: Re: ActiveMQ 5.16.x Master/Slave topology question On Tue, 2021-11-30 at 17:20:31 +0100, Vilius Šumskas wrote: >[...] > As an alternative, does anybody know if I can use non-HTTP SSL load balancer > and set client URI to something like ssl://loadbalancer_ho

Re: ActiveMQ 5.16.x Master/Slave topology question

grations? > > BR, > - Simon > > > -Original Message- > > From: Jean-Baptiste Onofré > > Sent: Tuesday, November 30, 2021 6:01 PM > > To: users@activemq.apache.org > > Subject: Re: ActiveMQ 5.16.x Master/Slave topology question > > > > Hi

Re: ActiveMQ 5.16.x Master/Slave topology question

rom: Jean-Baptiste Onofré > Sent: Tuesday, November 30, 2021 6:01 PM > To: users@activemq.apache.org > Subject: Re: ActiveMQ 5.16.x Master/Slave topology question > > Hi, > > masterslave: transport is deprecated. You can achieve the same with > randomize=false basically. > > Co

RE: ActiveMQ 5.16.x Master/Slave topology question

that's possible :)). -- Vilius -Original Message- From: Jean-Baptiste Onofré Sent: Tuesday, November 30, 2021 6:01 PM To: users@activemq.apache.org Subject: Re: ActiveMQ 5.16.x Master/Slave topology question Hi, masterslave: transport is deprecated. You can achieve the same w

Re: ActiveMQ 5.16.x Master/Slave topology question

Hi, masterslave: transport is deprecated. You can achieve the same with randomize=false basically. Correct: updateClusterClientOnRemove is only for network connection, but when you have active/active (so a real network). No, the clients won't be stuck: they will reconnect to the new master.

RE: ActiveMQ 5.16.x Master/Slave topology question

t: Tuesday, November 30, 2021 7:01 AM To: users@activemq.apache.org Subject: Re: ActiveMQ 5.16.x Master/Slave topology question Hi No need to use networkConnector with master/slave. Just use failover on the client side. So basically, 1. Brokers side, you shared the same filesystem (using NFS, LUN

Re: ActiveMQ 5.16.x Master/Slave topology question

Hi No need to use networkConnector with master/slave. Just use failover on the client side. So basically, 1. Brokers side, you shared the same filesystem (using NFS, LUN, whatever), and you configure kahadb to point on the same filesystem in activemq.xml 2. On client side, you can failover

ActiveMQ 5.16.x Master/Slave topology question

Hi, I‘m trying to setup a simple ActiveMQ 5.16.x master/slave cluster using shared filesystem option. I just need one broker running at any given time and a slave for HA. The filesystem part is clear and I have already configured it according to ActiveMQ requirements. What I don’t understand

RE: Master+slave+slave

one. (the first backupnode can be gone because it crashed or was stopped; or because it became the new master due to a failing original master) e. -Oorspronkelijk bericht- Van: Edson Richter Verzonden: vrijdag 4 juni 2021 14:58 Aan: users@activemq.apache.org Onderwerp: Master+slave+sl

Master+slave+slave

Hi! I’m trying to setup a cross DC setup with one master and two slaves. Servers are: Sc0b03 => master Pr0b03 => slave 1 Sp0b03 => slave 2 The relevante configuration is: On Master server: tcp://sc0b03:61616 tcp://pr0b03:61616 tcp://sp0b03:61616 xx

Re: [EXTERNAL] Re: Master-Slave being DB locked both

I'm not an NFS expert, but is vers=300 really correct? I don't think there's an NFSv300. Also, note that ActiveMQ offers the best support for shared-filesystem master-slave on NFSv4, whereas NFSv3 has undesirable behavior (described in h

Re: Master-Slave being DB locked both

I'm not an NFS expert, but is vers=300 really correct? I don't think there's an NFSv300. Also, note that ActiveMQ offers the best support for shared-filesystem master-slave on NFSv4, whereas NFSv3 has undesirable behavior (described in https://activemq.apache.org/shared-file-syst

Re: Master-Slave being DB locked both

Hi, If it’s on NFS, what’s your rsize/wsize and sync mode enabled ? Regards JB > Le 6 mai 2020 à 16:29, Jose Manuel Vega Monroy > a écrit : > > Hi there, > > With broker 5.15.0-1.el7.centos, looking like master and slave both brokers > keeping DB locked with NFS remote share. > > 2020-05-0

Master-Slave being DB locked both

Hi there, With broker 5.15.0-1.el7.centos, looking like master and slave both brokers keeping DB locked with NFS remote share. 2020-05-06 15:08:52,372 [main] INFO (AbstractApplicationContext.java:583) - Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@5025a98f: startup date [Wed May

Re: Any Solution for Activemq Split brain for Master Slave

umudi Venkatesha, Srinivas (Nokia - IN/Bangalore) wrote: > I have gone through the below page - > > > https://activemq.apache.org/components/artemis/documentation/latest/network-isolation.html > > But, how to use this in Wildfly Application Server's Artemis activemq. > Cur

Any Solution for Activemq Split brain for Master Slave

I have gone through the below page - https://activemq.apache.org/components/artemis/documentation/latest/network-isolation.html But, how to use this in Wildfly Application Server's Artemis activemq. Currently we have a master - slave configuration running and this scenario is occurring

Re: Connect connect master slave clustering in ActiveMQ 5

Unrelated, but you don't need to specify failover in this URI: uri="static:(failover:(tcp://localhost:61626)) Static networkConnectors retry automatically (unlike normal client connections), so you can use static by itself. Tim On Fri, Mar 20, 2020, 6:35 PM Matt Pavlovich wrote: > Nicky- > > T

Re: Connect connect master slave clustering in ActiveMQ 5

Nicky- The two instances are sharing a data folder, and ActiveMQ is treating the first broker that obtains the lock as the primary and the second as the failover (aka slave). You’ll need to configure the dynamicOnly="true" >networkTTL="2" >duplex="true" /> > > > and the tran

Connect connect master slave clustering in ActiveMQ 5

I have 2 amq brokers as amq1 and amq2. I have configured amq1 as with below configurations; and the transport connector as; In am2 I have add the following configuration; But still when I start the two servers one after other, the first starting broker starts and returns an

Re: Master/Slave setup over Loadbalancer

s the > request to > > activemq node on http transport port. > > > > We are trying to convert our setup to a HA solution using Master/slave > but > > we were not sure how we can use failover transport to include both the > > master and slave nod

Re: Master/Slave setup over Loadbalancer

t setup: https call to Loadbalancer--> LB forwards the request to > activemq node on http transport port. > > We are trying to convert our setup to a HA solution using Master/slave but > we were not sure how we can use failover transport to include both the > master and slave nodes in

Master/Slave setup over Loadbalancer

Our Current setup: https call to Loadbalancer--> LB forwards the request to activemq node on http transport port. We are trying to convert our setup to a HA solution using Master/slave but we were not sure how we can use failover transport to include both the master and slave nodes in the c

Re: Artemis master/slave startup results in two live broker

Hi all, I am running the exact same static configurations using 2.6.4 version but in a Kubernetes cluster and I see that I still end up with two live servers after the original live is brought down. Any insight on this? Thanks -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-

Artemis replication static connector master/slave failback with split brain avoidance and a reverse proxy

Hello I have a replication master/backup setup with static connectors, two nodes and failback. Both nodes are configured with a network-check-list to a third node to avoid split brain. I have also set up a reverse proxy in front of the master/slave artemis because a client of ours cannot be

Re: replicated static master/slave - which is the correct URI for an artemis-jms-client?

Thank you Justin. I can indeed see in your source code that this flag is being used all over the place. I am now using it and also using reconnectAttempts=-1 and things behave ok. I ran into the issue in one of the client environments where clients did not want to failover, as if locked in to the

Re: replicated static master/slave - which is the correct URI for an artemis-jms-client?

The "ha" parameter tells the client to use the backup information it receives from the broker so in case the original connection fails it will automatically connect (i.e. failover) to the backup. Without ha=true on your client URL you won't get true failover. I believe what you're seeing is just t

Re: ActiveMq Artemis Master/Slave

This turned out to be a typo in my configuration - underscore instead of a dash, so the configuration parser was unable to find the connector. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: replicated static master/slave - which is the correct URI for an artemis-jms-client?

So what exactly is the ha parameter for? Does it treat servers somehow differently? E.g. *non-ha* pool of servers, vs. *ha* pool of servers? Form what I am seeing, even without it, client fails over to slave after retrying master 5 times and then fail over to the slave... So the fail over is someh

Re: replicated static master/slave - which is the correct URI for an artemis-jms-client?

I'd say you're missing the ha flag. To enable failover you need to use "ha=true" in your URL. Otherwise the client won't know that it's connection to an HA (i.e. highly available) master/slave pair. Justin On Thu, Aug 1, 2019 at 6:35 AM mk666aim wrote: > Th

Re: replicated static master/slave - which is the correct URI for an artemis-jms-client?

Also, in a scenario where master server is started again, and backup server should fail back to the master from that moment onwards Should the client also reconnect to the master? It does not seem to be happening, as my client is still locked to the backup server. When I shut down backup server

Re: replicated static master/slave - which is the correct URI for an artemis-jms-client?

The below URL does not seem to work for me. Client basically never switches to the backup node. Isn't that what reconnectAttempts=-1 will cause? I used following URL before and the switching happened: *(tcp://master:61616,tcp://slave:61616)?reconnectAttempts=5* What am I missing? And what is th

Re: ActiveMq Artemis Master/Slave

I read the linked issue too, and as I understand that was to do with NFS. However, I am getting very similar issue when using shared JDBC store (MySQL). Error is slightly different though: I have traced it to this call here in the FailbackChecker: Seems the default connection is empty or wha

Re: ActiveMq Artemis Master/Slave

I read the linked issue too, anf as I understand that was to do with NFS. However, I am getting very similar issue when using shared JDBC store (MySQL). Error is slightly different though: Any help appreciated. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

replicated static master/slave - which is the correct URI for an artemis-jms-client?

Hi Justin,   thanks a lot for clarification. I couldn't find a documentation with all supported URI schemes and all supported options for the Artemis JMS core client. Maybe you have a link...   Frank

Re: replicated static master/slave - which is the correct URI for an artemis-jms-client?

Thanks for following up, Frank. I would expect a URL like this to work: (tcp://master:61616,tcp://slave:61616)?ha=true&reconnectAttempts=-1 Both "randomize" and "backup" are not used by the Artemis JMS core client. Also, the "failover://" schema is used by OpenWire clients, not Artemis JMS cor

replicated static master/slave - which is the correct URI for an artemis-jms-client?

Hello all,  there was an error in my broker.xml files on both master and slave. After correcting these, the following URI is working with the "ActiveMQ JMS Core Client" library (and also with the artemis command line clients), like it should.  (tcp://master:61616,tcp://slave:61616)?ha=true&rec

replicated static master/slave - which is the correct URI for an artemis-jms-client?

Hello,  I've followed the test setup and installed a replicated static master/slave environment (like documented here: https://github.com/jbossdemocentral/amq-ha-replicated-demo). Version is Artemis 2.7.0. Both master and slave processes start without errors.  Now I try to find out whi

Re: Master / Slave failover - Client connections don't re-connect - using CORE API

OK - I have it working. There was indeed a problem with the ActiveMQ servers master / slave configs in the broker.xml files for each. The sections , were entirely missing, and the only had the local host defined, and not the other one. Thank you Justin for pointing me in the right direction

Re: Master / Slave failover - Client connections don't re-connect - using CORE API

Thanks. It's running in a Docker container, so I "docker stop" it. I can see the log output as the slave takes over and starts up, and then I can log into the old slave's ActiveMQ management console. And, I can see that the client detects the down master and attempts reconnects. Having said tha

Re: Master / Slave failover - Client connections don't re-connect - using CORE API

One more thing... Since you're using share-store then you either need to really kill the broker (e.g. kill -9 ) to trigger failover or set true if you're stopping the broker gracefully, e.g.: true Justin On Mon, Jul 8, 2019 at 3:03 PM bob.sandif

Re: Master / Slave failover - Client connections don't re-connect - using CORE API

Sorry about the code not showing up. I edited the post to put it in. Thanks for the reply - a simple usage of your suggestion didn't work - but it did change the behaviour, so I'll pursue the possible values for the query params on the url specification. Bob. -- Sent from: http://activemq.228

Re: Master / Slave failover - Client connections don't re-connect - using CORE API

None of the code or configuration came through on your first email. In the second email it didn't come through either, but some of it is visible on the Nabble web page. That said, I think the problem is the URL you're using (i.e. "(tcp://activemq-1:61616,tcp://activemq-2:61616)"). You aren't speci

Re: Master / Slave failover - Client connections don't re-connect - using CORE API

Sorry - a couple of other things. The exception I get on the client (when I shut down the master ActiveMQ) and try to send a message to ActiveMQ is: I'm using a URL like this: I tried: but got an exception like this: -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f234

Master / Slave failover - Client connections don't re-connect - using CORE API

I have a (I think) simple master / slave setup of ActiveMQ servers, using shared file system. When I shut down the current master, it fails over to the slave, and when I then restart the original master, it becomes the standby - which is all just fine. I'm having problems on the client

Re: SMB 3.0 as shared filesystem for kahaDB in Master/Slave

Hi Cezkuj, Were you able to achieve? I am exploring ActiveMq Artemis Master and Slave configuration on Azure Files (SMB3.0) and would like to know whether you were be able to complete. Thanks -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: H/A replication master slave

> So does that mean that -- after shutting down master and then slave -- it's not enough to start the slave again and that the master server must be then started as well? That's not what I'm saying. I'm saying that if the master and slave both go down then *administrative intervention* is require

Re: H/A replication master slave

So does that mean that -- after shutting down master and then slave -- it's not enough to start the slave again and that the master server must be then started as well? Because, obviously, starting the master first isn't an option as it might have older data than its slave, right? -- Sent from:

Re: H/A replication master slave

>From what I can tell everything is working as designed. As the documentation [1] states: In the replication case, the backup just keeps waiting for a live server to pair with. Note that in replication the backup server does not know whether any data it might have is up to date, so it really c

Re: H/A replication master slave

Hi, below my test: 1) start master and slave; 2) send two messages, stored on master; 3) stop master; 4) slave is live and it has 2 messages; 5) stop slave; 6) restart slave but i haven't previous messages; Thanks in advance for the help! Kind regards, Gianfranco Aloi -- Sent from: http://act

Re: H/A replication master slave

I don't really understand what you mean by, "If the only node to start is the slave, i lose all information in the queue." Can you elaborate on this? How are you losing information? Justin On Mon, Jun 24, 2019 at 8:37 AM galoi wrote: > I'm using artemis ActiveMQ Artemis 2.9.0, and i configured

H/A replication master slave

I'm using artemis ActiveMQ Artemis 2.9.0, and i configured two nodes master and slave in replication HA. View Below: true true

Re: Failover Transport hangs forever on connection.start() in Master/Slave

Hi, Following is the stack trace for successful connection to activeMQ: # 2019-04-30 20:51:52 DEBUG TaskRunnerFactory:91 - Initialized TaskRunnerFactory[ActiveMQ Task] using ExecutorService: java.util.concurrent.ThreadPoolExecutor@6504e3b2[Running, pool siz

Re: Failover Transport hangs forever on connection.start() in Master/Slave

Can you upload the full stack dump from the client application when this happens as a GIST on github.com and send the link? It's OK to filter out any proprietary bits as long as all of the threads that have ActiveMQ in the call history are listed. BTW, the "oneWay" method sends a message over the

Re: Failover Transport hangs forever on connection.start() in Master/Slave

I am using activemq version 5.15.8. I see the issue when client first time tries to connect to activemq broker and if the randomly picked broker url happens to be slave, the call is stuck forever in FailoverTransport class at the following point: ## @Override publ

Re: Failover Transport hangs forever on connection.start() in Master/Slave

You haven't mentioned a version of your activemq, there were some issues with that in older versions... We're on 5.6.0 and above - no issues... See http://activemq.apache.org/failover-transport-reference -- Sent from: http://activemq.

Failover Transport hangs forever on connection.start() in Master/Slave

Hi,  I have Master/Slave broker url for failover transport as follows:  (ssl://brokerurl1:61616,ssl://brokerurl2:61616)?timeout=5000&startupMaxReconnectAttempts=5&maxReconnectAttempts=5   Client picks up one broker url at random, if the url picked up to connect at random is slave, the ca

cannot change password for 'system' user - master/slave cluster with NFS4 share, using kahadb

I am new to amq, so I apologize if this is a stupid question, but I need a hand. was able to test successfully: failover to the passive node when I shutdown the active node. Queues persist. admin page configured with AD integration. from admin page, can create a topic or queue, browse it,

ActiveMQ Master-Slave brokers - Puppet mcollective

Hi guys, I set up activemq based on this document https://puppet.com/docs/mcollective/current/deploy/middleware/activemq.html Everything worked fine until we got 6000 more servers subscribed. Sys memory: brokers config transport = 0.0.0.0:61616?jms.prefetchPolicy.all=10&

Re: JDBC driver with Failover (Master-Slave) MS SQL database

My last question in that three-year-old thread applies to you too: are you using a wrapper such as Tanuki that would detect the broker process exiting and respond by restarting the ActiveMQ process? This would be the expected way to handle this situation, so if you're not doing that, it's what I'd

Re: JDBC driver with Failover (Master-Slave) MS SQL database

I have the same issue with ActiveMQ. I have two nodes of AMQ and it is configured to use MS SQL with database cluster. When the database cluster fails over, my AMQ stops working and I need to re-start it manually to fix the issue. Could you please post how did you fix your issue? -- Sent from: h

Re: ActiveMq Artemis Master/Slave

I already addressed your question on Stack Overflow [1]. Take a look and respond there. Justin [1] https://stackoverflow.com/questions/54112308/warn-when-an-activemq-artemis-master-slave-pair-is-deployed-in-openshift On Wed, Jan 9, 2019 at 12:39 PM juan.mar...@techonrails.com < juan.

ActiveMq Artemis Master/Slave

Hi all, I´m trying to deploy an ActiveMQ Artemis Cluster as Master/Slave in Openshift. I have been able to connect both brokers (differents containers), I Persist the data folder of the brokers to share the fileSystem. In Slave container i received continually this Error: 2019-01-09 07:50

Re: SMB 3.0 as shared filesystem for kahaDB in Master/Slave

Hi! Sad to be the only one :(. I will try if approach suggested by you satisfies my needs (I don't want to overcomplicate whole setup) Thanks for response. I will bump it when I found easiest way to solve my problem :) Kind regards, Cezary -- Sent from: http://activemq.2283324.n4.nabble.com

Re: SMB 3.0 as shared filesystem for kahaDB in Master/Slave

You're the only person I've heard of trying to use a SMB share as the filesystem for a KahaDB master-slave configuration during the four years I've been watching this list, so it's quite possible that the file-locking semantics of SMB don't allow ActiveMQ to use SMB for lo

SMB 3.0 as shared filesystem for kahaDB in Master/Slave

Hi! Is it possible to run ActiveMQ in Master/Slave scenario using SMB as shared fs on Linux? Have anyone proved it to work? I've searched this mail list and other resources and have not found a lot of documentation on this topic. Few pages say that either it should work or it works onl

Re: Using AWS EFS as the shared file system for master/slave broker pair

Did you consider using Amazon MQ? This is standard ActiveMQ with all the infrastructure managed for you. https://aws.amazon.com/amazon-mq/ -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Using AWS EFS as the shared file system for master/slave broker pair

I'm not sure I understand >>>> that >>>> part. Thanks! >>>> >>>> >>>> thall wrote >>>>> There are a number of docker images for activemq, you will need to >>>> follow >>>>> the documentation for th

Re: Using AWS EFS as the shared file system for master/slave broker pair

t; > Make sure your docker image is using the latest version of activemq. >>> > You are going to need to change the data directory to be under the efs >>> > mount, and you are going to have to configure a pluggable storage >>> locker >>> > a

Re: Using AWS EFS as the shared file system for master/slave broker pair

r the efs >> > mount, and you are going to have to configure a pluggable storage locker >> > as well. >> > >> https://cwiki.apache.org/confluence/display/ACTIVEMQ/Pluggable+storage+lockers >> > < >> https://cwiki.apache.org/confluence/display/ACTIVEM

Re: Using AWS EFS as the shared file system for master/slave broker pair

play/ACTIVEMQ/Pluggable+storage+lockers > > < > https://cwiki.apache.org/confluence/display/ACTIVEMQ/Pluggable+storage+lockers> > ; > > https://activemq.apache.org/pluggable-storage-lockers.html > > > > -Tom > > > >> On Jul 18, 2018,

Re: Using AWS EFS as the shared file system for master/slave broker pair

https://cwiki.apache.org/confluence/display/ACTIVEMQ/Pluggable+storage+lockers > <https://cwiki.apache.org/confluence/display/ACTIVEMQ/Pluggable+storage+lockers>; > https://activemq.apache.org/pluggable-storage-lockers.html > > -Tom > >> On Jul 18, 2018, at 3:47 PM, av

Re: Using AWS EFS as the shared file system for master/slave broker pair

luggable+storage+lockers > < > https://cwiki.apache.org/confluence/display/ACTIVEMQ/Pluggable+storage+lockers > > > https://activemq.apache.org/pluggable-storage-lockers.html > > -Tom > > > On Jul 18, 2018, at 3:47 PM, avmpt wrote: > > > > I would like to use

Re: Using AWS EFS as the shared file system for master/slave broker pair

t 3:47 PM, avmpt wrote: > > I would like to use EFS as the shared file system when I set up a > master/slave broker pair. What changes would I need to make to the > persistence adapter to use the mounted EFS path? > > When I have > > > > > Would I

Using AWS EFS as the shared file system for master/slave broker pair

I would like to use EFS as the shared file system when I set up a master/slave broker pair. What changes would I need to make to the persistence adapter to use the mounted EFS path? When I have Would I need to change it to the path where EFS is mounted? Are there any additional

  1   2   3   4   5   6   7   8   9   10   >