Re: Active MQ cluster behind load balancer

Hi Emily, Let me illustrate: - if you use a load balancer (Cisco, Juniper, F5, ...), you will load balance the connections. With JMS, the messages are not directly sent via the connection, but via sessions inside a connection. So basically, when you use tcp, the same connection is used to prod

Active MQ cluster behind load balancer

Hello All, Need clarification on working of ActiveMQ cluster. When a network of brokers is created are the connectiosn also shared? For eg. If I make a connection with server1 can I use this object and createsession on server2. Will server2 know of the connection with server1. Regards, Emily

Re: Critical metrics to monitor over JMX?

The thing I'm generally most concerned about is whether messages are backing up on queues or in topic subscriptions, since that usually means a performance problem somewhere in the system. So that plus JB's suggestion of monitoring how usage compares to the various broker/store limits would be wha

Re: ActiveMQ Topic Messages Not Delivered

In the default configuration, ActiveMQ will auto-create a destination when a consumer subscribes to it or when a message is produced to it, whichever happens first. Brokers in networks of brokers subscribe to the consumer advisory topics (so they know where to route messages) but don't subscribe t

Re: ActiveMQ Topic Messages Not Delivered

Tim Bain wrote > Re: #1: Do you remember what the other two advisory topic names were? The other two I was seeing were ActiveMQ.Advisory.Producer.Topic.x and ActiveMQ.Adivsory.Expire.Topic.x . Looking at things this morning I'm also seeing the "Producer" topic as well. Maybe these topics

Re: AMQ CPP Consumer Receive() and receiveNoWait() does not return

On Thu, 29 Oct 2015 07:21:19 -0700 (PDT), JackOfAllTrades wrote: >I'm trying to update to AMQ CPP 3.9.0. > >The calls to the consumer receive() and receiveNoWait() will not return. >There are messages available on the queue. Older version 2.4.4 worked. > >Anybody have any thoughts on this? Can

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

Hi Tim, Thank you for your assistance and your quick response. As for the questions, let me try to explain better: 1. We have 2 ActiveMQ Services installed (A, B) on different machines (Amq1, Amq2) which are configured in ActiveMQ Failover configuration- Both relay on a single SQL database

RE: Get ActiveMQ broker version programmatically

Jan, If you're using jolokia with ActiveMQ, it's even simpler over Http: http://yourBroker:8181/hawtio/jolokia/read/org.apache.activemq:type=Broker,brokerName=amq/BrokerVersion Use GET, and make sure to set Basic Auth header if JMX security is enabled, -Original Message- From: Basmajian

RE: Get ActiveMQ broker version programmatically

You can do it via JMX, Attribute - BrokerVersion MBean - org.apache.activemq:type=Broker,brokerName= -Original Message- From: Jan Gargulák [mailto:jan.gargu...@trixi.cz] Sent: Monday, November 02, 2015 9:15 AM To: users@activemq.apache.org Subject: Get ActiveMQ broker version programma

Get ActiveMQ broker version programmatically

Hi, we need to get the broker version remotely through its API. Is there any way how to do it? We're on ActiveMQ v5.11.1. Thank you, Jan Gargulak -- View this message in context: http://activemq.2283324.n4.nabble.com/Get-ActiveMQ-broker-version-programmatically-tp4703591.html Sent from the Act

Re: Critical metrics to monitor over JMX?

This is the Decanter Kibana ActiveMQ dashboard: https://github.com/apache/karaf-decanter/blob/master/kibana/src/main/resources/app/dashboards/activemq.json You can see the filters on the JMX attributes. Regards JB On 11/02/2015 03:08 PM, Basmajian, Raffi wrote: Tim, I'm not worried about real

RE: Critical metrics to monitor over JMX?

Tim, I'm not worried about real-time volume, I'm more concerned about which metrics are important to monitor. We're using an agent on the broker to collect metrics; it's JMX-based and pushes metrics to remote storage. Though I like the jolokia REST interface for ad-hoc/casual use, I don't see it

Re: Critical metrics to monitor over JMX?

Keep in mind that JMX is slow and you're not going to get thousands of metric values per second. My experience was somewhere around 50 to 100 per second, though your mileage may vary. If you're worried that may not be enough, the Jolokia REST interface is supposed to be much faster. On Nov 2, 201

Re: Critical metrics to monitor over JMX?

Hi Raffi, I would monitor: - the JVM standard (threads, memory, etc) - the system usage percent usage (broker object name) - the pending messages (destination object names) It's what we described by default in Karaf Decanter for the ActiveMQ view. Regards JB On 11/02/2015 05:35 AM, Basmajian,

Re: Messages erroneously rejected as duplicates

On Sun, 1 Nov 2015 07:44:34 -0700, Tim Bain wrote: >This sounds like a bug. Since Tim Bish (the only person I've seen support >ActiveMQ-CPP) didn't comment on it here, please submit a bug report in >JIRA, ideally with your consumer code (better: a stripped down minimal >version that produces the