On 05/21/2015 03:14 PM, Darryl L. Pierce wrote:
Got an interesting bug I'm digging into currently.
In Ruby I've written analogs to the direct_* and simple_ send/recv
example apps. The simple versions all work well and can interact with
Python as expected.
However, the direct_recv.rb example isn't.
When the container starts listening for incoming direct connections, I
see
the following frames come in when the simple_send.rb client (or Python
analog) connects:
<- @open(16)
<- @begin(17)
<- @attach(18)
But what I don't see is the outgoing connection connections that occurr
in the Python version:
-> @open(16)
-> @open(17)
-> @open(18)
So the client connects but the flow never begins between the two. I'm
digging into the acceptor code but don't see where Ruby is behaving
differently from Python.
Any suggestions?
In python, it is the EndpointStateHandler, that is part of
MessagingHandler which is responsible for that. If ruby is doing
something similar, I'd start by checking if the equivalent handler is
being called.
