[
http://jira.jboss.com/jira/browse/JGRP-540?page=comments#action_12366905 ]
Bela Ban commented on JGRP-540:
-------------------------------
With me, if remove the 2 sleeps(), then it is hard to reproduce the failure. This is
probably because you run this on a multicore machine, whereas my laptop is a uniprocessor.
Anyway, it's good that we can reproduce this and I'll investigate this Friday.
I don't see why SynchronousQueue causes this; even if it doesn't enforce FIFO
that's not an issue as the take() will enforce FIFO. The take() method only returns
(and thus lets another thread run) when the task is completed...
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