Re: ActiveMQ – “Master/Slave” configuration with failover protocol

You need to give the batch file a task (start, stop, restart, etc.) as an argument. Tim On Sep 26, 2016 9:06 AM, "mathewvino" wrote: > Hi there > > i am trying with latest version of apache-activemq-5.14.0 to do the > Master/Slave failover > > Use the below tutorial

ActiveMQ – “Master/Slave” configuration with failover protocol

Hi there i am trying with latest version of apache-activemq-5.14.0 to do the Master/Slave failover Use the below tutorial which is straight forward which is on 5.8.0 https://www.javacodegeeks.com/2014/04/using-activemq-masterslave-configuration-with-failover-protocol.html Following steps did

Re: jconsole using activemq

Thanks Steve/Tim it works for me. All i did is add In the activemq.xml file, add useJmx="true" to the tag and make changes to activemq.bat set ACTIVEMQ_SUNJMX_START= -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.authenticate=false

Re: "Cannot send, channel has already failed" messages

Hi, I am getting the following error. Let me know. Thanks Ram.S -- View this message in context: http://activemq.2283324.n4.nabble.com/Cannot-send-channel-has-already-failed-messages-tp4654848p4716873.html

Re: Active MQ Shared File System Master Slave with Elastic File System

Please take a look at the comment I made on: https://issues.apache.org/jira/browse/AMQ-6441 I may know what the issue is. The particular client I am working with is running JDK 7. -- View this message in context:

activem-admin command is missing in 5.13.0 for linux

Hi, I have just installed 5.13.0 on my linux machine but i don't see activemq-admin command. Kindly guide on the same how can I get it. Thanks & Regards Shipra -- View this message in context:

Re: KAHADB clean up old log files

I will hijack this thread since I have almost the same problem. Log files the filling up disk and TRACE telling me: "not removing data file: XXX as contained ack(s) refer to referenced file: [XXX]" Running ActiveMQ 5.13.4. I hacked'n'slashed KahaDBJournalReader (would be great if the source code

Re: Messaging for temporary connected systems

This can be done with ActiveMQ using a hub-and-spoke topology on a network of brokers. The spoke brokers should use duplex connections to the hub so the hub broker doesn't need to enumerate them all. You can either embed a broker within each client or run standalone brokers at each spoke

Re: Iterate over non-persistent activemq expired messages in ActiveMQ.Advisory.Expired.Queue

>From http://activemq.apache.org/message-redelivery-and-dlq-handling.html: "By default, ActiveMQ will not place undeliverable non-persistent messages on the dead-letter queue." So unless you enable the processNonPersistent option described in that page, you can't. If you do enable that option,

Re: JMS exception during the Failover

If you switch your acknowledgement mode to AUTO_ACKNOWLEDGE and comment out your call to message.acknowledge(), does the behavior change? Client ack mode isn't very widely used, so it's possible there's a bug in the interaction between it and failover. Also, in your original post, you said that

Active MQ scalability

Hello, Im new to ActiveMQ and want to know suppose if my current server where active mq is installed supports 1K messages per sec. Now load gets increase and its upto 10K per sec. 1. What needs to be done to handle this much of load ? 2. Is scalability possible in active mq ? 3. If possible

Re: activem-admin command is missing in 5.13.0 for linux

Browsing jira I noticed the removal of this component. Didn't dive deeper, but it's no longer there. Probably the same things can be done, but in a different way. What would you like to do? What would you need the activemq-admin command for? -- View this message in context:

Re: ActiveMQ ReplicatedLevelDB corruption

Gave the system a weekend time to see if it could recover automatically... alas that's not the case. However, when I stopped all brokers, changed one of the brokers with 'replicas="1"' (rather than 3); started it (kind of single mode) and started the other brokers one by one so they could catch