[rabbitmq-discuss] STOMP Error?

[Darien Kindlund]

I believe the original perl Net::Stomp code I was using was properly
connecting and disconnecting -- the problem was more the fact that
this code was doing a connect(), send(), disconnect() operation
really, really quickly, with multiple perl processes doing this
operation simultaneously.  The STOMP adapter really doesn't like that.

As a follow-up, once I switched each perl process over to re-using
their existing STOMP connection, things worked much, much better.  As
such, I'm continuing development.  In your unit testing, you may want
to include rapid connect/disconnect behavior or otherwise explicitly
warn developers to avoid this scenario.

-- Darien

On Wed, Feb 11, 2009 at 6:55 AM, Tony Garnock-Jones <tonyg at lshift.net> wrote:
> Darien Kindlund wrote:
>>      Reason:     {{badmatch,{error,closed}},
>>                   [{rabbit_stomp,send_frame,2},
>>                    {rabbit_stomp,mainloop,1},
>>                    {rabbit_stomp,init,1},
>>                    {proc_lib,init_p,5}]}
>
> That's interesting! Are the clients disconnecting without issuing
> DISCONNECT? That's legal, but clearly the current adapter code isn't
> coping gracefully with the situation...
>
> Tony
>
>