[rabbitmq-discuss] 2.4.0 channel and connection close behavior

[Aaron Westendorf]

I can reliably reproduce. I have tcpdump output which is the easiest
for me to generate. If that's not helpful, then we'll just wait until
I can wrap this up and release it.

-Aaron

On Thu, Mar 31, 2011 at 9:22 AM, Matthew Sackman <matthew at rabbitmq.com> wrote:
> On Wed, Mar 30, 2011 at 09:44:05PM +0100, Matthew Sackman wrote:
>> Are there any errors in either of the logs when this happens? There may
>> well be something in the sasl log, but I think this is likely a bug.
>
> I've read through the code and I think it's fine. Constructing a test is
> a little tricky actually because most of our clients are "sensible" and
> make channel.close a synchronous blocking operation, thus it's difficult
> to send in the connection.close before getting the channel.close_ok
> back.
>
> If you can reliably make it happen, (and verify with our Tracer and/or
> wireshark), then it would be helpful if you could let us see the code.
>
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>



-- 
Aaron Westendorf
Senior Software Engineer
Agora Games
359 Broadway
Troy, NY 12180
Phone: 518.268.1000
aaron at agoragames.com
www.agoragames.com