[
https://issues.apache.org/jira/browse/QPID-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7374:
-----------------------------
Description:
Virtualhost Housekeeping is also currently responsible for transaction timeout.
Detecting transaction timeout is entirely a connection centric task and could
be reimplemented simply as an IO ticker. Transaction timeout would be better
implemented as a Ticker, which would awaken the connection if a idle/close
timeout is due.
was:
Housekeeping currently could hog resources, for instance a single run could TTL
a very large number of messages, starving other actors in the Broker or delay a
shutdown of a Broker or VirtualHost. It should be changed so that it chunks
work into reasonable chunks, rescheduling itself as necessary.
Housekeeping is also currently responsible for transaction timeout.
Transaction timeout would be better implemented as a Ticker, which would awaken
the connection if a idle/close timeout is due.
> Reimplement producer transaction timeout feature to utilise an IO ticker
> ------------------------------------------------------------------------
>
> Key: QPID-7374
> URL: https://issues.apache.org/jira/browse/QPID-7374
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: Future
> Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> Virtualhost Housekeeping is also currently responsible for transaction
> timeout. Detecting transaction timeout is entirely a connection centric task
> and could be reimplemented simply as an IO ticker. Transaction timeout would
> be better implemented as a Ticker, which would awaken the connection if a
> idle/close timeout is due.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
