Re: Availability of holdOnPublishEnabled attribute in Qpid Broker-J 0.32

[sidarthsc <si...@gmail.com>]

Could you explain how the logic behind the holdOnPublishEnabled attribute
works? For example, is there a thread that periodically iterates over all
messages in queues for which this attribute is enabled and releases, or
pushes those messages which are eligible for being processed?



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

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

Re: Availability of holdOnPublishEnabled attribute in Qpid Broker-J 0.32

[Keith W <ke...@gmail.com>]

On Tue, 12 Feb 2019 at 00:26, sidarthsc <si...@gmail.com> wrote:
>
> Could you explain how the logic behind the holdOnPublishEnabled attribute
> works? For example, is there a thread that periodically iterates over all
> messages in queues for which this attribute is enabled and releases, or
> pushes those messages which are eligible for being processed?

It is the responsibility of the virtualhost housekeeper (see
VirtualHostHouseKeepingTask and
org.apache.qpid.server.queue.AbstractQueue#checkMessageStatus).  The
period with which the housekeeper runs is defined by
virtualhost.housekeepingCheckPeriod so a message may remain held of
the queue by virtualhost.housekeepingCheckPeriod ms too long.
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

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