Discard messages for Slow consumers on "Queue"

Hi Docs, I have running Active MQ 5.8 and have setup VirtualDestinations (2 queues). One of the queue is slow and it is not discarding messages. Could some one please suggest how should I enable discarding messages for that queue ? please find below my code snippet: broker.setDeleteAllMe

ActiveMQ Multicast Network Connection Loop?

Hi, I have recently upgraded to 5.8.0 and I am noticing something weird when I use the multicast protocol for the network connector. Here is the relevant config (note that I am running in OSGi): When I set up my broker with this config, I am seeing the broker connect to itself:

Re: Random slow Subscribers - causing Topic to full - Solution ?

Currently I have 2 consumers set up - which are consuming from Queues. I have disabled producerflowcontrol, setMemoryLimit to 1, queueprefetch = 10, topicprefetch = 10. I have added infinite sleep in consumer1 and I ran the load test with 90 events. My expectation is consumer1 discarding all

Re: Random slow Subscribers - causing Topic to full - Solution ?

I was able to forward messages from Topics to Queue using VirtualDestination. But I am not able to figure out how do I configure my consumer to drop messages if they are consuming slow. I got below snippet from ActiveMQ documentation. Non-durable queues A slow consumer is not really an issue wit

Re: Camel & ActiveMQ

No performance impact. The component will use the factory under the covers. On Mon, Mar 18, 2013 at 6:34 AM, Bipin Jethwani wrote: > I have jaasAuthenticationPlugin defined for my embedded activemq broker > instance (and it is working fine), and then I have camel context defined > with activemq

Re: ACtiveMQ CMS and JMSXUserID property

I agree if it is classified as a bug and not as unimplemented feature that has work around. I will create a jira and the test case per your request. Thanks again... -- View this message in context: http://activemq.2283324.n4.nabble.com/ACtiveMQ-CMS-and-JMSXUserID-property-tp4664762p4664830.htm

Re: duplex flag cannot be set via JMX for NetworkConnector

Can you please open a JIRA? configuration of the network connector when creating it (and tuning the bridge once its created) is fairly limited at the moment. On Mon, Mar 18, 2013 at 5:19 AM, Nitesh wrote: > I am trying to add network connector via JMX. I want to turn duplex > attribute > to tru

Re: How are advisory topics different from durable topics ?

Advisory toipcs replay existing state to new consumers so that a new consumer doesn't miss events in the past. It won't replay every single event, just the events that would create the "current" state, ie in your case, the existing queues. This behavior is built into the advisory destination implem

Camel & ActiveMQ

I have jaasAuthenticationPlugin defined for my embedded activemq broker instance (and it is working fine), and then I have camel context defined with activemq component exposing many beans for remote invocation. Now I noticed from other posts here that there are two ways to make camel authenticate

Re: ActiveMQ & Camel

Hi James, You know I was setting jaas for my activemq broker and then creating camel context by providing the login credentials to actievemq connection factory, but reading your post I saw that there's another way of doing that by providing the credentials to activemq component rather, so wanted t

Timer already Exception

I Have the following exception Exception in thread "main" javax.jms.JMSException: Timer already cancelled. at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49) I use apache-activemq-5.5.1 and jdk1.6.0_26 Regards -- View this message in context: http://activ

duplex flag cannot be set via JMX for NetworkConnector

I am trying to add network connector via JMX. I want to turn duplex attribute to true. I see this attribute is read only. Is it done on purpose or is it a issue. -- View this message in context: http://activemq.2283324.n4.nabble.com/duplex-flag-cannot-be-set-via-JMX-for-NetworkConnector-tp466

How are advisory topics different from durable topics ?

Hi, We user AdvisorySupport.QUEUE_ADVISORY_TOPIC for listening to all existing/new queue creation events and then dynamically create a DefaultMessageListenerContainer for that queue. Thus every time we restart consumer hosts, all listeners get created. How does this work ? I need to create some