Re: Backup Server - Failover

Yes, the web console will show you those things. But it won't show you the things I mentioned, such as which consumers are subscribed to a topic, or the list of not just which clients are currently connected but also some (all?) of the clients that have previously connected, which is why I suggest

Using wireFormat

Is there an issue of mixing wireFormat.x with non wire format configuration items for client failover connection transport options? failover:(tcp://localhost:61616,tcp://remotehost:61616)?wireFormat.MaxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=2000&randomize=false&startu

Re: Backup Server - Failover

The Web Admin console for each server (primary and backup) identifies all the topics/Number of Consumers/Enqueued Messages/Dequeued Messages. What about the randomize=false option? Shouldn't that disable secondary? thanks !! -- View this message in context: http://activemq.2283324.n4.nabble

Re: Backup Server - Failover

JConsole has an MBeans tab for viewing the JMX beans for the app it attaches to, and you can drill down to the topic and then see what consumers are attached to it. You might take a look there to see if there are any consumers attached that you're not aware of, or any durable subscriptions for con

Re: Backup Server - Failover

There were no topics when the clients started. At startup the primary has consumers but secondary does not. For each publish request the numbers of Enqueued message values increase on both primary and secondary servers. I'm using the randomize=false option, so what is causing secondary to even be i

Re: Backup Server - Failover

Are the numbers in the Enqueued column increasing, or just non-zero? If it's not increasing, could you have stranded messages on secondary when you took primary down (and everyone failed over to backup) and then consumers eventually migrated back to primary? (See the Stuck Messages section of htt

Backup Server - Failover

I'm using the following client configuration : failover:(tcp://primary:61616,tcp://secondary:61616)?initialReconnectDelay=3000&maxReconnectDelay=2000&randomize=false&startupMaxReconnectAttempts=10 When we publish a message we see the message being published to both primary and secondary servers b

Re: Question about Network Brokers

I'm confused by what you're asking, so let me try to explain what I would expect, and see if that answers your questions. You will have producers, which all connect to a broker (call it BP). That broker will have networkConnectors to the broker for Version1 consumers (BV1) and the broker for Vers

Re: Question about Network Brokers

Thanks for the reply, I have a doubt, I in my client define a broker that have a netwotk connector to my activeMQServer (is a name). In my activeMQServer, Would I need define a broker that listen this message? I could define a broker to listen and then then other that have netwotk connector to se

ActiveMQ NMS client and DTC transactions

Hi, I would like to know what the situation is regarding the use of DTC transactions with the NMS client. I have read in numerous places that NMS does not reliably support DTC; however, nowhere am I able to find a detailed explanation of exactly what the issue is, either in terms of how it mani

Re: Prefetch Limit ignored with a reconnecting Durable Subscriber

Hi again, i have verified, that the durable subscriber on reconnect is configured correctly, when I set keepDurableSubsActive to false on the broker. Best regards Andreas On 02/10/14 12:03, Andreas Gies wrote: Thanks Gary, to me it looks like configure is not being called when the subscribe

Re: Auto creation of Advisory topic and message being post to it.

Thanks all for clarifying this. -Regards, Atgroxx On Wed, Oct 1, 2014 at 4:38 PM, Andreas Gies [via ActiveMQ] < ml-node+s2283324n4686060...@n4.nabble.com> wrote: > Hello, > > within your broker you have the advisory support enabled which causes > the additional > topics to be created. You can fi

Re: Prefetch Limit ignored with a reconnecting Durable Subscriber

Thanks Gary, to me it looks like configure is not being called when the subscriber reconnects. I ll try to trace that later. I'll create a JIRA for now. Thanks Andreas On 02/10/14 11:40, Gary Tully wrote: that looks like a bug and you should raise a jira. however the broker config will onl

Re: Prefetch Limit ignored with a reconnecting Durable Subscriber

that looks like a bug and you should raise a jira. however the broker config will only override the default value, so a client provided value will take precedence if it is specified. It seems the client does not specify a value, the broker 5 is used the first time, and the default on subsequent r

How to migrate queue messages from one instance of ActiveMQ to another

Hi We have an activeMQ instance that has too much data (30GB) in it's persistance store and it's causing a major problem. We can address the long term issue through the use multi kaha db adapter Managing persistent store space