[
https://issues.apache.org/jira/browse/QPID-7975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209352#comment-16209352
]
Kim van der Riet commented on QPID-7975:
----------------------------------------
The problem lies again with the {{linearstore::journal::InactivityFireEvent}}
class. The state machine in this {{TimerTask}} child class is getting stuck
because no path was added for the class to move from state {{FLUSHED}} to state
{{FIRED}} for cases where an external flush call (as provided by the AMQP 0-10
messages) arrives before a timer fire. This prevented the timer from being
reset and from firing in the normal manner.
> [linearstore] Sending durable messages using AMQP 1.0 and 0-10 concurrently
> causes high latency for 1.0 messages
> ----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7975
> URL: https://issues.apache.org/jira/browse/QPID-7975
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Reporter: Kim van der Riet
>
> When durable messages are sent to the same queue using both AMQP 1.0 and 0-10
> concurrently, a condition is triggered where the store no longer flushes the
> 1.0 messages. When this condition is triggered, the 1.0 messages are flushed
> by the 0-10 activity on the queue, or if there is none, then the messages are
> never flushed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
