[
http://jira.jboss.com/jira/browse/JGRP-426?page=comments#action_12354588 ]
Bela Ban commented on JGRP-426:
-------------------------------
The current design doesn't handle #3; in this case M2 will have to wait for M1
although M2 was sent by a different sender...
Multiplexer: test concurrent processing
---------------------------------------
Key: JGRP-426
URL:
http://jira.jboss.com/jira/browse/JGRP-426
Project: JGroups
Issue Type: Task
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.5
4 unit tests:
- Message M1 blocks for 10 seconds. Message M2 doesn't block and should get processed
immediately
#1 Sender A sends M1 to S1 and M2 to S1. M2 should wait until M1 is done
#2 Sender A sends M1 to S1 and M2 to S2. M2 should get processed immediately and not have
to wait for M1 to complete
#3 Sender A sends M1 to S1 and sender B sends M2 to S1. M2 should get processed
concurrently to M1 and should not have to wait for M1's completion
#4 Sender A sends M1 to S1 and sender B sends M2 to S2. M1 and M2 should get processed
concurrently
--
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