Why is there an unused Queue Dispatch Policy?

In org.apache.activemq.broker.region.Queue, there is a field dispatchPolicy = new RoundRobinDispatchPolicy(); Also, there are getters and setters for neither the getter nor the field is ever used. Why is that? A custom dispatch policy for queues seems to be exactly why I need but according to

Re: Dispatch policy for ActiveMQ with new message groups? [

is actually similar to another idea I had. I was hoping there was some magic we could find in ActiveMq that we weren't aware. Thanks again for your response. I will take a look at the code. -- View this message in context: http://activemq.2283324.n4.nabble.com/Dispatch-policy-for-Act

Re: Dispatch policy for ActiveMQ with new message groups? [

modify. By the way, is a network of brokers in use? Things get more complicated in that case. -- View this message in context: http://activemq.2283324.n4.nabble.com/Dispatch-policy-for-ActiveMQ-with-new-message-groups-tp4687812p4687861.html Sent from the ActiveMQ - User mailing list archive

Re: Dispatch policy for ActiveMQ with new message groups? [

Also note the "can dispatch" logic checks for a match on the consumer group (yes, the message in the consumer group iterates over all of the consumers rather than bypassing the loop). -- View this message in context: http://activemq.2283324.n4.nabble.com/Dispatch-policy-for-ActiveM

Re: Dispatch policy for ActiveMQ with new message groups? [

uot;. So, which consumer gets the next group assignment is really based on the last consumer to which a message was dispatched. The code in question is in Queue.java, doActualDispatch() and assignMessageGroup(). -- View this message in context: http://activemq.2283324.n4.nabble.com/Dispatch-pol

Re: Dispatch Policy

not change anything in activemq, is there any way to change the dispatch policy to process based scheduling of consumer just by making changes in activemq_broker.xml or any of the camel/Spring config (bundle-context, bundle-context-camel) files? or make consumers poll (without actually setting

Re: Dispatch Policy

prefetch > limit equal 0 before of Spring framework. > > Any ideas that might help asynchronous consumers to poll for messages > without setting prefetch limit to 0? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Default-Dispatch-

Re: Dispatch Policy

messages without setting prefetch limit to 0? -- View this message in context: http://activemq.2283324.n4.nabble.com/Default-Dispatch-Policy-and-Pending-message-Limit-Strategy-tp2365262p3697021.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Dispatch Policy

oses the concurrent consumers to push the > messages to. This seems to be the case even when the prefetch is modified to > 1. I cannot use a prefetch of 0 since I'm using Spring. I've tried changing > the dispatch policy to Simple Dispatch in the activemq configuration xml but >

Re: Dispatch Policy

ified to 1. I cannot use a prefetch of 0 since I'm using Spring. I've tried changing the dispatch policy to Simple Dispatch in the activemq configuration xml but I continue to see the same behavior. Is there any way I can configure activemq to push a message to the first available consume

Re: Dispatch Policy

Thank you so much for your reply. I will definitely try it out. Just one confusion, can you explain how simple dispatch policy works? Because I am not able to find much documentation on it. Can you give me a brief description. -- View this message in context: http://activemq.2283324.n4

Re: Dispatch Policy

> I am confused with different dispatch policies. There seems to be few > dispatch policies available in activemq along with bunch of properties that > can be changed to achieve different purposes. > > RoundRobin dispatch policy is not working for me. My messages are getting > stuck

Dispatch Policy

Hi, I am confused with different dispatch policies. There seems to be few dispatch policies available in activemq along with bunch of properties that can be changed to achieve different purposes. RoundRobin dispatch policy is not working for me. My messages are getting stuck with the thread

Re: Default Dispatch Policy and Pending message Limit Strategy

The code is the best reference for defaults as they can change across versions. If want specific behavior, it is safest to provide explicit configuration for your broker via the xml configuration or programatically when you create your broker. For the default dispatch policy, see: line 68 of

Default Dispatch Policy and Pending message Limit Strategy

Dear all, I'm wondering what are the defaults for these two configuration parameters. I know the options for Dispatch Policy are: - SimpleDispatchPolicy: Simple dispatch policy that sends a message to every subscription that matches the message. - StrictOrderDispatchPolicy: Dis

Custom Dispatch Policy

How would one load a custom dispatch policy for a particular queue (the various consumers have differing 'costs' and 'capabilities' and the lowest cost consumer with the required capabilities needs to be selected)? -- View this message in context: http://www.nabble.com/Cu

Dispatch Policy Question

w this message in context: http://www.nabble.com/Dispatch-Policy-Question-tf3660142s2354.html#a10227336 Sent from the ActiveMQ - User mailing list archive at Nabble.com.