[
https://issues.apache.org/jira/browse/QPID-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369362#comment-16369362
]
Alex Rudyy commented on QPID-8091:
----------------------------------
I reviewed the changes made in commits [
https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=876bcb7 ], [
https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=63c315f ], [
https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=d57815f ] and [
https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=fa2b1ff ]. They
look good to me, though, I made further changes in documentation in commit [
https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=2303a76e2cb92ef0bcf282851c9cf1db4fd2eb00
] . I am going to port all JIRA changes into 7.0.x.
> [Broker-J] [AMQP 1.0] Store transaction timeout feature
> -------------------------------------------------------
>
> Key: QPID-8091
> URL: https://issues.apache.org/jira/browse/QPID-8091
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
>
> Berkeley JE's design means that once a transaction has begun, its internal
> cleaner is unable to clean beyond the point the transaction started in the
> transaction log. Other transaction work continues as normal, but the disk
> space utilisation can't shrink until the long running transaction is
> completed. In an extreme case, disk space can be exhausted.
> This has consequence for long running store transactions in Qpid. For 0-x,
> the transaction timeout features allows the the length of time a transaction
> may be open or idle to be constrained, thus limiting the harmful effects of a
> long running store transaction.
> For robustness, that features needs to be implemented on AMQP 1.0 too. A
> decision needs to be made about the correct course of action to be taken when
> a long running transaction exceeds the threshold. The transaction
> coordinator link could be closed with an error or the entire connection
> closed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
