[ http://jira.jboss.com/jira/browse/JGRP-181?page=comments#action_12341748 ] Bela Ban commented on JGRP-181: ------------------------------- One idea is to have a thread pool handle incoming messages, so that for messages A1, B10, B11, B12, A2, {A1,A2} and {B10-12} can be processed concurrently with respect to each other. However, in the following case: A1, A2, A3, A4, B1. Let's assume we have a threadpool of 2 configured. In this example, thread-1 (T1) will handle A1 and T2 will handle A2. T2 will have to block until A1 has been processed. This is bad, as we could deliver B1 on a separate thread in the meantime. So, using a threadpool for each message, regardless of the message's sender, isn't good. We should rather categorize messages by sender, e.g. have 1 queue per sender: {A1-4} and {B1}, and have T1 process the queue {A1-4} and T2 process the queue {B1}. Need to investigate whther this is possible with QueuedExecutor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira