Hi, We use Artemis 1.1 with clients on WildFly 10.1.0 final instances. We would like to provide more robust and high available environments. I tested 1 artemis broker with 2 WF servers that listen same queue by consumers. When one of WF instaces is under load (throws runtimexceptions on onMessage process or occurs latency due to some unexpected behaviours), I can see that artemis observes those slow consumers via slow-consumer detection. In those circumstances, we are looking for effective/proactive actions for this situation rather than killing consumer sessions or notifying a management message as built-in features. Is there a way (with artemis built-in features) to be able to consume next (including redelivering) jms messages by other consumers that belong to other WF instance/s via blacklisting/rating or something else? Thank you in advance. Brgds
-- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
