It occurs to me that I wasn't completely clear: - Of course the priority mailbox must break message ordering in some general sense. Else it wouldn't be a priority mailbox at all! - But it is highly surprising to me that it should break ordering for messages of equal priority between a sender-receiver pair.
On Friday, 9 January 2015 17:58:40 UTC, David Hotham wrote: > > Hi, > > We've been tracking down a bug in which reading from a TCP stream was > getting all messed up. > > It turns out that we see the problem only when our actor handling > Tcp.Received messages is using an UnboundedPriorityMailbox; the default > mailbox doesn't exhibit any problem. > > I believe that the issue is that the UnboundedPriorityMailbox is backed by > a PriorityBlockingQueue; and that, per the documentation for that class, > "Operations on this class make no guarantees about the ordering of elements > with equal priority". > > That is, it seems that the UnboundedPriorityMailbox breaks the guarantee > of message ordering per sender–receiver pair. In our case, the result > being that different chunks of the TCP data stream arrive not in the order > in which they were read from the wire. > > Does this analysis seem to be correct? > > If yes, is it a bug? Would you like me to raise a ticket? > > Thanks! > > David > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
