[
http://jira.jboss.com/jira/browse/JGRP-539?page=comments#action_12366618 ]
Bela Ban commented on JGRP-539:
-------------------------------
The issue that sometimes messages have not been received by everyone after a flush phase
is that the Multiplexer has its own thread pool, which is not flushed on FLUSH. This
means, although a message was delivered correctly, the thread pool may not yet have passed
it on to the application.
FLUSH: incorrect set of messages after flush
--------------------------------------------
Key: JGRP-539
URL:
http://jira.jboss.com/jira/browse/JGRP-539
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Vladimir Blagojevic
Fix For: 2.5
MultiplexerTest.testVirtualSynchrony() creates 2 MuxChannels, then sends 10 messages to
each (so each should have 20 messages total).
The Channel.startFlush() is called, after 5 secs stopFlush() is called automatically.
This returns true, an indication that flush succeeded.
However
- we see messages being received *after* flush has run
- we do not have the same and correct number of elements in both channels
--
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