quot;write" bit will be lost.
This then fits with my symptoms and those in the other thread: the
TcpConnection will be left waiting for a ChannelWritable message that never
happens.
As I say, I'm not yet convinced that this is in fact what I'm seeing - this
theory is so far based
I think my idea is wrong, so long as the SerializedSuspendableExecutionContext
does indeed do what it says it does and serialize tasks.
The question as to whether anything ever became of the earlier thread
stands.
On Thursday, 18 December 2014 19:25:41 UTC, David Hotham wrote:
>
&
all.
>
> Are you using latest Akka 2.3.8? There have been multiple fixes to akka-io
> since Akka 2.3.2. What OS are you running your code on?
>
> On Fri, Dec 19, 2014 at 1:26 AM, David Hotham > wrote:
>>
>> I think my idea is wrong, so long as the
>> SerializedSuspe
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 i
ty 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
nderstand that it can be surprising, but I wouldn't
> call it a bug -per se-, since it is not a promise that was violated.
>
> If you happen to have, or come by, a performant version of a PriorityQueue
> with the semantics you described, please don't hesitate to share it.
&g
I've submitted a first stab at an implementation at pull request #16634.
On Friday, 9 January 2015 21:02:21 UTC, √ wrote:
>
>
>
> On Fri, Jan 9, 2015 at 9:40 PM, David Hotham > wrote:
>
>> Of course it's normal and expected that a PriorityQueue returns equal
