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 crucial importance. We currently have a setting of 10 concurrent consumers on the main application queue, which is just enough for the application to be able to chew all of the events in time. However, from time to time, we do receive a bulk of low important messages, for which the processing time is not of such a great importance. By that, I mean they should definitely yield to the normal priority ones, but should not sit on the queue forever or until expired. And this is exactly what happens: since the application is constantly under the load of processing the normal important messages, whenever we get a bulk of low priority ones, they very hardly seem to get the consumer to process them, because all of the consumers are always busy with the normal priority messages. This finally leads to a large portion of low priority messages expiring from the queue after an hour. As you remember me mentioning earlier, the grouping feature is also of great importance, because all of the messages hold the information about a resource that should never be accessed concurrently, which is why I was trying to find a way to somehow give the low priority messages a chance to be processed, without compromising the processing time of the normal messages and while maintaining the exclusive access to the common resource. I hope this makes it more clear now. Do you have any ideas or suggestions on how to achieve that? Regards, Frankie -- View this message in context: http://activemq.2283324.n4.nabble.com/Selective-consuming-of-priority-messages-with-message-groups-tp4704813p4704927.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
