Thanks for the quick responses...
Mixed processing of messages with different priorities is not a problem for
us. What we have to prevent is, that an online request is only processed
(with a huge delay) after all batch messages (several thousands) are
processed.
Writing in different queues is possible. Than, my JMS consumer route would
looks like:
{code}
from("activemq://queue:inbox.online?concurrentConsumers=5")
.to("direct:inbox");
from("activemq://queue:inbox.batch?concurrentConsumers=5")
.to("direct:inbox");
from("direct:inbox")
.processRef("myProcessor")
.to("activemq://queue:outbox");
{code}
Thanks,
Christian
--
View this message in context:
http://old.nabble.com/good-solution-to-work-with-jms-message-priority-tp28778639p28779260.html
Sent from the Camel - Users mailing list archive at Nabble.com.
