qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cajus Pollmeier <ca...@naasa.net>
Subject Re: What exactly does LinkClosed mean?
Date Tue, 17 Apr 2012 07:40:29 GMT
Am 16.04.2012 10:46, schrieb Gordon Sim:
> On 04/13/2012 08:27 AM, Cajus Pollmeier wrote:
>> Hi,
>>
>> I'm using the python-qpid package to do some messaging. Sometime -
>> especially after some time of inactivity, the exception "LinkClosed" 
>> is
>> raised when sending a message:
>>
>> ...
>> File "/usr/lib/python2.7/dist-packages/qpid/messaging/endpoints.py",
>> line 836, in send
>> self._ecwait(lambda: self.linked)
>> File "/usr/lib/python2.7/dist-packages/qpid/messaging/endpoints.py",
>> line 51, in _ecwait
>> self.check_closed()
>> File "/usr/lib/python2.7/dist-packages/qpid/messaging/endpoints.py",
>> line 793, in check_closed
>> raise LinkClosed()
>>
>> Reading the source I'm not quite sure what that means - is the 
>> sender
>> connection down? Or is the receiver bored of dealing with the 
>> sender?
>>
>> What would be the correct way to deal with that?
>
> Is there anything in the broker logs? Any error messages in 
> particular?

Nothing more than the stacktrace above. I can't find any hints in the 
qpidd.log. Currently waiting to get the error again to have the exact 
time where it happens.

> Does your application have multiple threads accessing the sender?

Yes, it has. Sadly the problem only occurs after a day or more.

Thanks,
Cajus

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message