[
http://jira.jboss.com/jira/browse/JGRP-540?page=comments#action_12367088 ]
Vladimir Blagojevic commented on JGRP-540:
------------------------------------------
I also noticed that as soon as task is run on callers thread we run into reordering
problems. If non-bound LinkedBlockingQueue is used test succeeds consistently. However, if
LinkedBlockingQueue is bound to 5-10 or so elements it is very likely that task will be
run on callers thread. If this happens testOrdering fails. I also verified that when using
SynchronousQueue we often end up running on callers thread.
Multiplexer: ordering issue
---------------------------
Key: JGRP-540
URL:
http://jira.jboss.com/jira/browse/JGRP-540
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Vladimir Blagojevic
Fix For: 2.5
Sometimes messages from the same sender are not delivered in the correct order, the test
that shows this (happens infrequently) is MultiplexerTest.testOrdering().
When disabling the Multiplexer thread pool (-Djgroups.mux.enabled=false), everything
works fine, so I suspect this is a thread pool issue in the Multiplexer
(FIFOMessageQueue).
--
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