You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Matt Broadstone <mb...@gmail.com> on 2015/05/19 21:37:21 UTC
qpidd forced heartbeat
Hi All,
Is it possible to configure qpidd to force incoming connections to use
heartbeats? I can't seem to find much on this online or in "qpidd --help",
other than a setting for federation link heartbeats.
Cheers,
Matt
Re: qpidd forced heartbeat
Posted by Gordon Sim <gs...@redhat.com>.
On 05/20/2015 07:02 PM, Matt Broadstone wrote:
> On Wed, May 20, 2015 at 4:34 AM, Gordon Sim <gs...@redhat.com> wrote:
>
>> On 05/19/2015 08:54 PM, Matt Broadstone wrote:
>>
>>> Unfortunately the amqp library we are working with in C# doesn't currently
>>> support setting the heartbeat interval.
>>>
>>
>> But it does support them internally if requested by the peer?
>
>
> Yeah it does, I actually figure out a way to modify the open frame to
> enable an idle timeout (it was undocumented). It would still be really
> great feature to be able to force this from the broker side, would you guys
> be interested in that (as in should I file a ticket)?
I can certainly see it would be useful in some situations and having a
JIRA doesn't hurt. Just to set expectations though, I'm not sure when I
myself would get to implementing that at present.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpidd forced heartbeat
Posted by Matt Broadstone <mb...@gmail.com>.
On Wed, May 20, 2015 at 4:34 AM, Gordon Sim <gs...@redhat.com> wrote:
> On 05/19/2015 08:54 PM, Matt Broadstone wrote:
>
>> Unfortunately the amqp library we are working with in C# doesn't currently
>> support setting the heartbeat interval.
>>
>
> But it does support them internally if requested by the peer?
Yeah it does, I actually figure out a way to modify the open frame to
enable an idle timeout (it was undocumented). It would still be really
great feature to be able to force this from the broker side, would you guys
be interested in that (as in should I file a ticket)?
Cheers,
Matt
>
>
> The particular issue I'm running
>> into involves a number guest VMs being run in libvirt keeping tcp
>> connections open to qpidd indefinitely after they have been destroyed
>> (force shutdown). This results in the default max-connections to qpidd
>> being reached in short order. Is there some other way to avoid this type
>> of
>> behavior from the qpidd side, aside from just restarting the service
>> periodically?
>>
>
> You could use QMF to periodically close some connections. Using qpid-stat
> -c you can see the idle time for each, plus the host connected from.
>
> The only supplied tool that can close a connection is qpid-tool which is a
> bit clunky tbh, but it would not be difficult to write a custom script e.g.
> to close connections that were idle for more than a given timeif that would
> be any use.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: qpidd forced heartbeat
Posted by Gordon Sim <gs...@redhat.com>.
On 05/19/2015 08:54 PM, Matt Broadstone wrote:
> Unfortunately the amqp library we are working with in C# doesn't currently
> support setting the heartbeat interval.
But it does support them internally if requested by the peer?
> The particular issue I'm running
> into involves a number guest VMs being run in libvirt keeping tcp
> connections open to qpidd indefinitely after they have been destroyed
> (force shutdown). This results in the default max-connections to qpidd
> being reached in short order. Is there some other way to avoid this type of
> behavior from the qpidd side, aside from just restarting the service
> periodically?
You could use QMF to periodically close some connections. Using
qpid-stat -c you can see the idle time for each, plus the host connected
from.
The only supplied tool that can close a connection is qpid-tool which is
a bit clunky tbh, but it would not be difficult to write a custom script
e.g. to close connections that were idle for more than a given timeif
that would be any use.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpidd forced heartbeat
Posted by Matt Broadstone <mb...@gmail.com>.
On Tue, May 19, 2015 at 3:45 PM, Gordon Sim <gs...@redhat.com> wrote:
> On 05/19/2015 08:37 PM, Matt Broadstone wrote:
>
>> Hi All,
>>
>> Is it possible to configure qpidd to force incoming connections to use
>> heartbeats? I can't seem to find much on this online or in "qpidd --help",
>> other than a setting for federation link heartbeats.
>>
>
> No. At present qpidd just goes along with whatever the clients decide with
> regards to heartbeats.
>
>
Unfortunately the amqp library we are working with in C# doesn't currently
support setting the heartbeat interval. The particular issue I'm running
into involves a number guest VMs being run in libvirt keeping tcp
connections open to qpidd indefinitely after they have been destroyed
(force shutdown). This results in the default max-connections to qpidd
being reached in short order. Is there some other way to avoid this type of
behavior from the qpidd side, aside from just restarting the service
periodically?
Matt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: qpidd forced heartbeat
Posted by Gordon Sim <gs...@redhat.com>.
On 05/19/2015 08:37 PM, Matt Broadstone wrote:
> Hi All,
>
> Is it possible to configure qpidd to force incoming connections to use
> heartbeats? I can't seem to find much on this online or in "qpidd --help",
> other than a setting for federation link heartbeats.
No. At present qpidd just goes along with whatever the clients decide
with regards to heartbeats.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org