Re: Selective consuming of priority messages with message groups

Hi guys, Thank you all for the suggestions; you sure taught me some new stuff ;-) I'll take those as a reference and will try to work out a new model for processing the messages in order to avoid the problem this whole discussion was started because in the first place. Cheers, Frankie -- View

Re: Selective consuming of priority messages with message groups

Hi Tim, Thanks for the feedback. The idea with the low and normal priority message separation arouse as a consequence of the main business process in the application. The application works in such a way that it is constantly fed by the normal priority events, for which the processing time is of

Re: Selective consuming of priority messages with message groups

Hi Jose, I'm using the prioritizedMessages=true because of the JMS grouping feature. In the application I'm running, one of the most important features is that messages with the same group ID are not processed in parallel, thus the message grouping ensuring the same consumer always gets the mess

Re: Selective consuming of priority messages with message groups

Hi All, Here's an update to the point Three: > Third, use a JMX viewer such as JConsole to look at the subscriptions on > that queue. Find the subscription that isn't working (#1) and see whether > it's present and whether its selector looks correct. See whether any > messages have been disp

Re: Selective consuming of priority messages with message groups

Hi Tim, Thanks a lot for the reply and the suggestions. Please find some of my comments inline. Regards, Frankie Tim Bain wrote > First, shouldn't you be expecting thread 2 to consume message 1? > > [Frankie] The thread numbers were symbolic only. In real life the numbers > would be something

Selective consuming of priority messages with message groups

Hi All, I'm having issues with a little piece of the code which is supposed to selectively consume the messages from a queue, using the message priority as the selector value. In addition to that, the grouping of messages is also being used. The prioritization policy is defined for the broker:

Re: Problem using custom defined deadletter queue

Hi, Thank you for your reply! I managed to solve the problem by simply upgrading to the new version of Camel (2.5) which eliminated all of the symptoms described above. Regards, Frankie -- View this message in context: http://activemq.2283324.n4.nabble.com/Problem-using-custom-defined-deadlett

Re: Problem using custom defined deadletter queue

Hi, I've got some new findings regarding the problem above. I manage to figure out that the cause to the problem is the .inOut() at the beginning of the "direct:start" route. If I comment out the .inOut(), than, upon exception and 3 retries, the messages end up in my custom defined DEADLETTER que

Problem using custom defined deadletter queue

Hi everybody, I have an issue using the ActiveMQ with Camel's dead letter channel error handler. The error handler is defined as follows: errorHandler(deadLetterChannel("activemq:DEADLETTER") .onRedelivery(new RedeliveryProcessor()) .maximumRedeliveries(3)