Re: Network of brokers and priority network links

way that I can set the base consumer priority in the xml config? > So that messages prefer to travel through certain brokers? > > Thanks again, big help. > > > From: Tim Bain > Sent: 03 November 2021 11:40 > To: ActiveMQ Users > Subject:

Re: Network of brokers and priority network links

Sent: 03 November 2021 11:40 To: ActiveMQ Users Subject: Re: Network of brokers and priority network links Use static:(failover:(stuff))?maxReconnectAttempts=0. Sorry for not remembering that it needed to be wrapped in static:(), the masterslave transport has mostly eliminated direct use of the fai

Re: Network of brokers and priority network links

hUpdateException; nested > PropertyAccessExceptions (1) are: > PropertyAccessException 1: > org.springframework.beans.MethodInvocationException: Property 'uri' threw > exception; nested exception is java.io.IOException: DiscoveryAgent scheme > NOT recognized: [failover] > > > As said before

Re: Network of brokers and priority network links

r transport to > be available on network connectors, but it isn't. The closest thing is the > masterslave transport, which does not have fail-back (priority URI) > capabilities. If you try to use the failover transport (discovery agent) > then an exception will be thrown. > &g

Re: Network of brokers and priority network links

f you try to use the failover transport (discovery agent) > then an exception will be thrown. > > Thanks again for the help, it's very much appreciated. > > > > From: Gary Tully > Sent: 02 November 2021 10:04 > To: users@activemq.a

Re: Network of brokers and priority network links

@activemq.apache.org Subject: Re: Network of brokers and priority network links there is one tweak with org.apache.activemq.network.NetworkBridgeConfiguration#setConsumerPriorityBase which could be used to bias the fast links, set that to -1 for the fast links and the others will default to -5, so ev

Re: Network of brokers and priority network links

irm whether > this can be done. > > Thanks again > > > From: Jean-Baptiste Onofre > Sent: 01 November 2021 16:46 > To: users@activemq.apache.org > Subject: Re: Network of brokers and priority network links > > Hi Paul, > > If you are using ActiveMQ 5.x, you can de

Re: Network of brokers and priority network links

. Thanks again From: Jean-Baptiste Onofre Sent: 01 November 2021 16:46 To: users@activemq.apache.org Subject: Re: Network of brokers and priority network links Hi Paul, If you are using ActiveMQ 5.x, you can decrease network priority to allow local consumers first

Re: Network of brokers and priority network links

Hi Paul, If you are using ActiveMQ 5.x, you can decrease network priority to allow local consumers first and fallback to remote brokers else. Is it what you are looking for ? Regards JB > Le 1 nov. 2021 à 17:37, Paul Burgess a écrit : > > Hi, > > I'm trying to configure a network of brokers

Re: Network of Brokers: cannot forward messages back to the broker from which they came

Find the solution. need to add enableAudit="false" in policyEntry -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Network of Brokers: cannot forward messages back to the broker from which they came

Thanks Tim Actually I have already included the following configuration as per document, it didn't work . Thanks -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Network of Brokers: cannot forward messages back to the broker from which they came

Please see the Stuck Messages section of http://activemq.apache.org/networks-of-brokers.html. Tim On Tue, Mar 5, 2019, 10:06 PM xing wrote: > The ActiveMQ version is 5.15.2 > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >

Re: Network of Brokers: cannot forward messages back to the broker from which they came

The ActiveMQ version is 5.15.2 -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Network of brokers and destination policies

Sounds like you're on the right path. If you're worried about being constrained by your available memory but don't want to restrict your producers and the fast application, you could send the messages to a persistence store on disk instead, to allow you to store more of them. Tim On Aug 11, 2017

Re: Network of brokers and destination policies

I'm primarily concerned about running out of space in broker memory. And we're not load-balancing between the applications; they are completely different, but both consume from some of the same topics that the clients publish to. Application 1 can fall behind when processing some of those messages

Re: Network of brokers and destination policies

What resources are you concerned about? Are you trying to load-balance the work across the two applications (i.e. you're concerned about CPU and about pre-allocating messages to a particular application), or are you worried about running out of space in the brokers' message stores? Or something els

Re: Network of brokers and destination policies

Here's a simplified diagram of my broker network: Application 1 and Application 2 both both use messaging internally. Their messages do not need to be distributed across the broker network. The applications consume message

Re: Network of brokers and destination policies

Thank you very much Tim. That is enough information to get me started thinking about this. It wasn't clear to me if the brokers had separate policies or if the same policy was communicated between brokers via administrative messages. I will almost certainly take you up on the offer of more specifi

Re: Network of brokers and destination policies

There's no one-size-fits-all answer here. The basic thing to know is that destination policies are specific to a given broker and the presence of a given policy on one broker doesn't cause another broker to automatically apply the same policy. Beyond that, how you configure each broker in an NoB d

Re: Network of brokers: consumers not synchronized

Some news on that: in the meantime, we have switched to only using static bridges in our project for connection of the mobile brokers to the back office. Is much more stable now. However, there is still some problem which shows up now and then: sometimes the back office broker "forgets" to start t

Re: Network of brokers: problem with duplex="false" for static bridges

Hi Tim, thanks for clarifying this. I may have expressed it not precisely in my answer: the problem exactly was that for the broker1_broker2_simplex bridge, when sending messages to a queue which is initially only known by broker 2 (because only there a consumer exists for this queue), sometimes d

Re: Network of brokers: problem with duplex="false" for static bridges

You've misunderstood the duplex setting. Setting the 1-2 link as simplex from the 1 side means that messages can go from 1 to 2 but not from 2 to 1 (unless you define a reciprocal connection in the 2 broker, but we're not considering that case here). It has nothing to do with applying a condition (

Re: Network of brokers: problem with duplex="false" for static bridges

Hi Jakub, thanks for the explanation! I was not aware that this even overrides the duplex="false" setting. But thinking about it again, it makes sense, since the duplex setting is relevant for the sync direction of consumers, not for the push direction / filtering of messages. So no other way tha

Re: Network of brokers and forwarding performance

Auke, Pooling your connections is definitely a good thing, but since you say that the system still exhibits the performance slowdown, your next step is what I said in my first response: to characterize which OS resource (CPU, network, disk, memory) is the limiting one, and on which broker or clien

Re: Network of brokers and forwarding performance

Hi Tim,Thank you for your replies.I've found one bug in our software: We didn't used a PooledConnectionFactory, which caused every message to be produced to mq2 setup a new connection to mq2. I've fixed this in the meanwhile and repeated my tests; the results were somewhat better (+1m/s), but not s

Re: Network of brokers and forwarding performance

BTW, I thought from your description that mq2 was a publish-only node, but you said you're testing performance by consuming from it. Can you please describe again how you're using the nodes, using the words "publish" and "consume" instead of the ambiguous word "receive"? Tim On Apr 25, 2017 7:14

Re: Network of brokers and forwarding performance

Quoting from an email I posted in another thread a few days ago: When a system is slow, there's always something (or several somethings, rotating between them) that is the limiting resource. I'd start by trying to determine what that resource is, using standard OS monitoring tools (top and the lik

Re: Network of Brokers - Connected but messages are not received on second broker

Messages exist one one and only one active broker at a time. If that happens to be the one you shut down, that message doesn't exist until you start the broker again. Your question about why you aren't seeing the message on both brokers at once sounds like you're still expecting clustering behavi

Re: Network of Brokers - Connected but messages are not received on second broker

Thank you Tim !, I do see that both brokers work as independent entities. But I can't tell which client on either broker processed these messages. When one broker, say broker 1 comes down or is stopped for upgrades, are the messages available on broker 2 also? Right now when a producer sends messa

Re: Network of brokers: consumers not synchronized

Saw it again. - The backoffice broker had shut down the connection (Channel was inactive for too (>3) long). - The mobile broker logged "Transport failed, not attempting to automatically reconnect; java.io.EOFException" and "bridge to stopped" - One second later, the mobile broker tries r

Re: Network of Brokers - Connected but messages are not received on second broker

You seem to be expecting your network of brokers to behave like a cluster. ActiveMQ doesn't support clustering; the closest we come is master/slave groups, but only one broker is active at a time so that's completely different. In a network of brokers, each broker is an independent entity that con

Re: Network of Brokers - Connected but messages are not received on second broker

I am using the java classes from ActiveMQ apache-activemq-5.14.1\examples\openwire\java Publisher and Listener. Modified Listener code to use Queue foo.bar on 61616 , and on Publisher queue foo.bar at 63616: Web Console at 61616 shows : Name Number Of Pending Messages Number Of Consumers M

Re: Network of Brokers - Connected but messages are not received on second broker

Show the client code. -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-Brokers-Connected-but-messages-are-not-received-on-second-broker-tp4720116p4720117.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Network of brokers: consumers not synchronized

I'll check this next time the issue shows up. But I'm pretty sure that if the connection is there on TCP level, it can be to nothing else than one of the two backoffice brokers, since only these are defined in the connection URI for the network connection. But anyways a good idea to check whether t

Re: Network of brokers: consumers not synchronized

So I was thinking about something more like netstat, to answer the question at the TCP layer. I've never used Karaf, but the documentation doesn't seem to provide a way to do that from within the container, but at a minimum you can run netstat on the host on which Karaf is running. I'm wondering w

Re: Network of brokers: consumers not synchronized

Hello, found the right command: activemq:query | grep -A 10 -B 10 networkConnectors. And the problem occurred again, so I could check this. The network connector is present on the mobile broker, but the web console of the backoffice broker doesn't show a connection. Regards, Jochen -- View th

Re: Network of brokers: consumers not synchronized

Hi Tim, how can I see the outbound connection on the mobile broker? I only have the activemq commands in the karaf shell, and neither activemq:bstat nore activemq:dstat show the connections. On the backoffice broker, I'm not sure, but I think that no connection was shown (I will have to wait until

Re: Network of brokers: consumers not synchronized

When the problem occurs, do you see an outbound network connection from the mobile broker to the backoffice broker? Does it go to the right host (i.e. backoffice1) at the right IP address? And do you see a corresponding inbound connection on the backoffice1 broker? Also, is it expected that the

Re: Network of brokers: consumers not synchronized

Hi Tim, first the respectve lines from karaf.log (the mobile broker is running in Karaf). You can see the successful connection at 04:46:01,955. Then, bit before 05:37:11, the mobile radio connection obviously was lost (I can also see this from a process which monitors the ppp connection - reporte

Re: Network of brokers: consumers not synchronized

Just to be clear: you get "Successfully connected to ssl://..." each time the connection fails, and never when it succeeds. Right? Can you please provide the filename and line number from that log line? Tim On Nov 14, 2016 5:33 AM, "jochenw" wrote: > Hi, > > in the meantime, I have digged bit

Re: Network of brokers: consumers not synchronized

Also, can you please give the couple of lines that precede the one you quoted in the bad case, to help us see how the broker got to that point? Tim On Nov 14, 2016 8:29 AM, Tim Bain wrote: Just to be clear: you get "Successfully connected to ssl://..." each time the connection fails, and never

Re: Network of brokers: consumers not synchronized

Hi, in the meantime, I have digged bit deeper into that. I can see from the logs, that when the mobile radio network connectivity breaks, after 30 seconds both brokers close the connection and the network broker bridge is stopped. Then the network connector tries to reconnect. Most of the time, af

Re: Network of brokers setup error

Mike, The biggest issue with geographically distributed systems is the latency introduced by the distances between your locations. You'll definitely want to tune your TCP stack, including computing an adequate TCP buffer size for the bandwidth-delay product

Re: Network of brokers setup error

Thanks Tim I have it working now with the masterslave option. Question: I'm setting up a masterslave cluster in Germany, China and other US Based locations is there any best practices for distributed clusters? Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Networ

Re: Network of brokers setup error

The static:failover: transport pair only works for networkConnectors when you specify the maxReconnectAttempts=0 option on the failover transport. This is not needed for client connections, only for broker-to-broker networkConnectors. Or you could just use the masterslave: transport, which is synt

Re: Network of brokers setup error

Additional info I left out. This is running ActiveMQ 5.14 in a SQL lock / Kahadb configuration on Windows 2012 core servers. -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-brokers-setup-error-tp4715603p4715604.html Sent from the ActiveMQ - User mailing lis

Re: Network of Brokers with load balancing

Nothing about your setup seems obviously wrong. Enabling JMX and using a JMX viewer such as JConsole is typically the best way to troubleshoot issues like these. First just check that a connection exists between B1 and B3. Then see if the subscription from B3 to B1 (or vice versa) exists on the

Re: Network of Brokers with load balancing

I have used discoveryuri and uri properties to set my network of brokers. Example : * […] * -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-Brokers-with-load-balancing-tp4712

Re: Network of brokers - Duplex or not?

Non-duplex connections can allow you to use the same config file for both brokers (if everything else about their configuration is the same), whereas with a duplex connection you have to either have two config files or you get two duplex connections. Having a separate connection in each direction

Re: Network of brokers problems

Thank you for all your replies. After a restart during server maintenance (of server3) things are now working strangely enough, I have no idea why unfortunately. To answer your questions: No, we don´t specify a TTL for the messages so I assume some default value is used. No, there shouldn´t be a

Re: Network of brokers problems

If the messages are being dequeued, they are getting consumed. Is there any other client connecting to server3 that might be consuming the messages? Are enqueue and dequeue counts on servers 1 and 2 changing? -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-br

Re: Network of brokers problems

Attach a JMX viewer such as JConsole to each broker on the failing path, and look at whether you have the consumer you expect on the queue in question. What you find will determine what to look at next. Tim On Nov 18, 2015 3:22 AM, "magnusT" wrote: > Hi, > > We have three servers running active

RE: Network of brokers problems

r 18, 2015 7:29 AM To: users@activemq.apache.org Subject: RE: Network of brokers problems [ EXTERNAL ] Hi Devlin, and thank you for your reply. I´m sorry if I´m confusing the terminology here. What we are trying to achieve is exactly what is happening when I send a message to server1 or server2.

Re: Network of brokers problems

2015-11-18 11:07 GMT+01:00 magnusT : > Hi, > > We have three servers running activemq in a network of brokers > configuration. The general idea of our setup is to have messages sent on one > server replicated to the other two. > > For this purpose we have setup composite queues (named *.composite)

RE: Network of brokers problems

Hi Devlin, and thank you for your reply. I´m sorry if I´m confusing the terminology here. What we are trying to achieve is exactly what is happening when I send a message to server1 or server2. We want to send one message to ALL other servers automatically (without the client sending the messaging

RE: Network of brokers problems

What are you trying to achieve? You mentioned "replication" and "forwarding" interchangeably, which is confusing. Message replication is a function of the persistence adapter, not network of brokers. Sent from my Verizon Wireless 4G LTE smartphone Original message From: mag

RE: Network of Brokers - Putting/Getting from a queue

com>] Sent: Sunday, October 04, 2015 09:42 PM Central Standard Time To: users@activemq.apache.org Subject: RE: Network of Brokers - Putting/Getting from a queue I'm not 100% sure if duplex works with SSL. Glad you're making progress :-) Raffi -Original Message- Fro

RE: Network of Brokers - Putting/Getting from a queue

I'm not 100% sure if duplex works with SSL. Glad you're making progress :-) Raffi -Original Message- From: barry.barn...@wellsfargo.com [mailto:barry.barn...@wellsfargo.com] Sent: Sunday, October 04, 2015 10:06 PM To: users@activemq.apache.org Subject: RE: Network of Brokers

RE: Network of Brokers - Putting/Getting from a queue

! Regards, Barry -Original Message- From: Basmajian, Raffi [mailto:rbasmaj...@ofiglobal.com] Sent: Sunday, October 04, 2015 8:52 PM To: users@activemq.apache.org Subject: RE: Network of Brokers - Putting/Getting from a queue Barry, If you're using SSL, do something like

RE: Network of Brokers - Putting/Getting from a queue

er 04, 2015 8:25 PM To: users@activemq.apache.org Subject: RE: Network of Brokers - Putting/Getting from a queue [ EXTERNAL ] Importance: High Our brokers are SSL enabled. Clients connect to it with the transport connector nio+ssl with no issues. This being the case I would think I would have to use

RE: Network of Brokers - Putting/Getting from a queue

Message- From: Tim Bain [tb...@alumni.duke.edu<mailto:tb...@alumni.duke.edu>] Sent: Saturday, October 03, 2015 03:49 PM Central Standard Time To: ActiveMQ Users Subject: Re: Network of Brokers - Putting/Getting from a queue OK, so if you don't see a subscription by Broker B on the TE

Re: Network of Brokers - Putting/Getting from a queue

om Broker A is not forwarded to it. > > Regards, > > Barry > > -Original Message- > From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain > Sent: Friday, October 02, 2015 1:21 AM > To: ActiveMQ Users > Subject: RE: Network of Brokers - Putting/Gettin

RE: Network of Brokers - Putting/Getting from a queue

from Broker A is not forwarded to it. Regards, Barry -Original Message- From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain Sent: Friday, October 02, 2015 1:21 AM To: ActiveMQ Users Subject: RE: Network of Brokers - Putting/Getting from a queue Have you done the

RE: Network of Brokers - Putting/Getting from a queue

e on BrokerA? > > Regards, > > Barry > > > -Original Message- > From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain > Sent: Thursday, October 01, 2015 10:20 AM > To: ActiveMQ Users > Subject: RE: Network of Brokers - Putting/Getting from

RE: Network of Brokers - Putting/Getting from a queue

@activemq.apache.org Subject: RE: Network of Brokers - Putting/Getting from a queue Could this be an issue? BrokerA is where the consumer listens for the message. BrokerB is where the message is placed on the TEST queue. When the client app connects to BrokerA to listen, the MDB automatically creates

RE: Network of Brokers - Putting/Getting from a queue

, October 01, 2015 10:20 AM To: ActiveMQ Users Subject: RE: Network of Brokers - Putting/Getting from a queue Stop testing with a producer; it's completely irrelevant. Messages traverse a network of brokers because they are pulled by consumers, not because they are pushed by producer

RE: Network of Brokers - Putting/Getting from a queue

a dynamic queue called TEST? > > Regards, > > Barry > > > -Original Message- > From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain > Sent: Thursday, October 01, 2015 9:13 AM > To: ActiveMQ Users > Subject: RE: Network of Brokers - Putting/Getting

RE: Network of Brokers - Putting/Getting from a queue

Subject: RE: Network of Brokers - Putting/Getting from a queue On Oct 1, 2015 7:02 AM, wrote: > > Have you disabled advisory messages and/or explicitly included/excluded any destinations? > I have added nothing in the activemq.xml file to exclude advisory messages, etc. > > An

RE: Network of Brokers - Putting/Getting from a queue

ards, > > Barry > > > -Original Message- > From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain > Sent: Thursday, October 01, 2015 8:56 AM > To: ActiveMQ Users > Subject: RE: Network of Brokers - Putting/Getting from a queue > > Your assumption is co

Re: Network of Brokers: XAException on Failover

BTW, I'm not convinced that a different network topology will avoid the exception you first asked about. Someone who knows XA transactions (which is not me, sorry) needs to look at that. On Oct 1, 2015 7:06 AM, "Tim Bain" wrote: > A network of brokers can be used for HA as long as the network to

Re: Network of Brokers: XAException on Failover

A network of brokers can be used for HA as long as the network topology will remain fully connected in the face of N failures (for whatever value of N you choose to support, probably 1) and the clients' failover URIs will always contain a live broker in the face of the same failure(s). But you cou

RE: Network of Brokers - Putting/Getting from a queue

-Original Message- From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain Sent: Thursday, October 01, 2015 8:56 AM To: ActiveMQ Users Subject: RE: Network of Brokers - Putting/Getting from a queue Your assumption is correct, networks of brokers allow messages to be forwarded

RE: Network of Brokers - Putting/Getting from a queue

on TEST if it > connects on Broker B, even though the queue is defined on Broker A. > Is my assumption incorrect? If so, how do we accomplish this design? > > > Regards, > > Barry > > > -Original Message- > From: Basmajian, Raffi [mailto:rbasmaj...@ofiglobal.co

RE: Network of Brokers - Putting/Getting from a queue

gards, Barry -Original Message- From: Basmajian, Raffi [mailto:rbasmaj...@ofiglobal.com] Sent: Thursday, October 01, 2015 8:45 AM To: users@activemq.apache.org Subject: RE: Network of Brokers - Putting/Getting from a queue Post your config and client code, otherwise, we're shooting i

RE: Network of Brokers - Putting/Getting from a queue

Post your config and client code, otherwise, we're shooting in the dark :-) -Original Message- From: barry.barn...@wellsfargo.com [mailto:barry.barn...@wellsfargo.com] Sent: Thursday, October 01, 2015 7:58 AM To: users@activemq.apache.org Subject: RE: Network of Brokers - Pu

RE: Network of Brokers - Putting/Getting from a queue

asmajian, Raffi [mailto:rbasmaj...@ofiglobal.com] Sent: Wednesday, September 30, 2015 3:07 PM To: users@activemq.apache.org Subject: RE: Network of Brokers - Putting/Getting from a queue Barry, No, not from the client perspective, there is no special designation. Provided config permits message flow

Re: Network of Brokers - Putting/Getting from a queue

That's all true when the consumer is connected or when a network of brokers is statically configured. If no consumer is currently connected to a dynamically configured NOB, messages will stay on the broker to which they're first published until a consumer connects, at which point they'll be forwar

RE: Network of Brokers - Putting/Getting from a queue

Barry, No, not from the client perspective, there is no special designation. Provided config permits message flow between A and B, messages should flow in the direction of the connector config. Raffi -Original Message- From: barry.barn...@wellsfargo.com [mailto:barry.barn...@wellsfar

Re: Network of Brokers: XAException on Failover

Maybe I'm not using the network of brokers in the correct manner. Should a network of brokers be used for HA, or just scalability and load balancing? We are not concerned with the loss of a few messages if one broker fails; however, we want to make sure there is not a single point of failure in

Re: Network of Brokers: XAException on Failover

I did mean 5.12. -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-Brokers-XAException-on-Failover-tp4702355p4702359.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Network of Brokers: XAException on Failover

Please tell me you meant 5.12, not 5.1.2. On Sep 26, 2015 5:08 PM, "mhempleman" wrote: > Jboss 6.1 EAP > ActiveMQ 5.1.2 > > I'm trying to connect Jboss to an ActiveMQ high availability cluster. When > I kill one ActiveMQ server and Jboss fails over to the backup server > everything works as expe

Re: Network of Brokers with one standalone and two embedded brokers on producer and consumer

Figured out the problem. I have to do connector.setNetworkTTL(2); On Fri, Jun 19, 2015 at 1:52 PM, pubudu gunawardena wrote: > Hi All, > > I have the following setup. There is a producer which sends messages > to an embedded broker. There is a consumer that consumes messages from > an

Re: Network of Brokers recommendations

Hi, Thanks for the reply. My earlier distinction was sloppy, I ought to have written something like 'partially connected mesh' vs. a complete graph. I was trying to distinguish between a topology where nodes are only connected to immediate neighbors, and therefore may always be required to trav

Re: Network of Brokers recommendations

Your understanding of this is good and you've got the right concepts here. The only two reasons I can think of that you shouldn't use a mesh (which I think is the same as a complete graph, though you drew a distinction between the two in your email so maybe there's a difference I'm not understandin

Re: Network of brokers with multiple worldwide data centers

You probably already figured this out, but that setting should be on any machines at either end of a connection across a high-latency network link. So definitely your brokers, but also any hosts of consumers that connect to a broker across a high-latency link. This setting is especially important

Re: Network of brokers with multiple worldwide data centers

Thank you for the reply Tim. I think we are going with a maser/slave setup at each dc but the main hub datacenter will have the config that notes all other data centers. Is it recommended to do the same with the other activemq.xml configs to point back to the hub, in case the hub goes down? We

Re: Network of brokers with multiple worldwide data centers

I'd strongly recommend setting the net.ipv4.tcp_slow_start_after_idle = 0 kernel parameter for any machine on either end of a high-latency network link; you don't really want the congestion window closing simply because the link isn't being used, but this is especially troublesome for high-latency

Re: Network of brokers with multiple worldwide data centers

Let me also add the systems at each datacenter are behind F5 load balancers. Is this a good practice or should we avoid the load balancers? -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-brokers-with-multiple-worldwide-data-centers-tp4693158p4693160.html Sent

Re: Network of brokers as a cluster

As I understand it, the text you quoted only applies if replayWhenNoConsumers=false. With replayWhenNoConsumers=true (as you have it), you should get all messages delivered from all brokers that are up, but you still won't get messages from brokers that are down until they come back up. So I thin

Re: Network of brokers as a cluster

Hi, I also tested durable subscriber on a network of 2 brokers and you are correct this case can also happen, from the documents on durable subscription: "However, if the subscriber disconnects and reconnects to broker A, any messages sent by P while the subscriber was away will be stuck on B unti

Re: Network of brokers as a cluster

As far as I know, this behavior would happen with simple topics and simple queues just as much as with virtual topics; this is a result of ActiveMQ's fundamental architecture, not something specific to virtual topics. The architecture of ActiveMQ ensures that any broker only knows about its own me

Re: Network of brokers as a cluster

Hi, I guess this is a real problem with networks of broker and virtual topics, I thought it could solve the problem of messages getting stuck when one of the brokers go down. I guess I will go on a simple topic and if my consumer goes down and reconnects he will only gets new messages (not durabl

Re: Network of brokers as a cluster

What you're describing sounds like what I warned about in my last paragraph: messages are getting routed to broker1 while the consumer is offline, which means they exist in broker1's message store and not anywhere else in the network of brokers. When broker1 goes offline, those messages don't exis

Re: Network of brokers as a cluster

thanks for the quick answer. my problem with the virtual topic with 2 brokers is this: consumer has a failover url of the 2 brokers, brokers are connected in duplex mode, replayWhenNoConsumers="true" 1. I have a consumer connected to broker1 2. each message that is sent to broker 1 or 2 is receive

Re: Network of brokers as a cluster

Yes, you can have a pair of brokers that are both active at the same time and that both have their own independent message store (not master/slave with a shared message store). You'll need to configure the brokers so they can talk to either other (either a duplex networkConnector from one to the o

Re: Network of brokers and protocol

On 07/10/2014 04:55 AM, moorsel wrote: Hi, I am trying to connect two different broker instances using a networkbrokerconnector. One of the brokers is ActriveMQ but the other is not but supports AMQP 1.0 so I would like to instruct the networkconnector to use AMQP in stead of openwire. Is this po

Re: Network of brokers problem

I'm not sure whether scheduling should persist across a broker network this way - and I can see many reasons that would lead to problems. To achieve redundancy with your brokers this way, look at a Master/Slave setup (I recommend shared filesystem master/slave). -- View this message in context:

Re: Network of brokers not picking up messages

Queue has 3 consumers and all those are of other MQ network of brokers. Pre-fetch is 1000 In activemq.xml there is only one broker defined with NetworkConnectors as On Thu, Jan 24, 2013 at 2:21 PM, Christian Posta wrote: > You'll need to post some more details... configs for the brokers,

Re: Network of brokers not picking up messages

You'll need to post some more details... configs for the brokers, which broker you're putting the message on, which broker has the consumers, etc. On Thu, Jan 24, 2013 at 3:13 PM, Mohit Anchlia wrote: > Could it be because of pre-fetch? It's set to 1000 and the messages are > less than 800. Not

Re: Network of brokers not picking up messages

Could it be because of pre-fetch? It's set to 1000 and the messages are less than 800. Not sure if it has something to do with that and how it works with network of brokers. On Thu, Jan 24, 2013 at 1:42 PM, Mohit Anchlia wrote: > I use network of brokers and in the admin UI I see the connections

  1   2   3   >