[rabbitmq-discuss] CRITICAL:pika.connection:Attempted to send frame when closed

[Gavin Roy]

Each thread needs its own connection, not channel.

On Wed, May 28, 2014 at 11:34 PM, shilpa karkera
<shilpa.karkera at finoux.com> wrote:

> Kindly look into the following issue. The threads are properly managed.
> On Wednesday 28 May 2014 12:04 PM, shilpa karkera wrote:
>> Okay, now I have reconfigured my entire code:
>>
>> Now each queue has its own channel. Thus when I open 3 browser tabs 
>> for my application. It starts 3 threads each having its own channel.
>> However, it still gives the same error.
>>
>>
>> On Wednesday 28 May 2014 09:11 AM, shilpa karkera wrote:
>>> Yep, got it! Thank you for the explanation. checking it out right away!
>>>
>>>
>>> On Tuesday 27 May 2014 08:33 PM, Steve Powell wrote:
>>>> What Michael meant to type is:
>>>>
>>>> On 27 May 2014, at 14:05, Michael Klishin <mklishin at gopivotal.com 
>>>> <mailto:mklishin at gopivotal.com>> wrote:
>>>>
>>>>> Each thread
>>>>> should have its own /*_channel_*/(e.g. open one right after it is 
>>>>> started), then
>>>>> you won't have this connection error. 
>>>>
>>>> Steve Powell [/Cell/: +44-7815-838-558]
>>>> /    Good design/ [...]/is as little design as possible. /Dieter Rams
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140528/476c76d2/attachment.html>