[
https://issues.apache.org/jira/browse/QPID-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365186#comment-15365186
]
Keith Wall commented on QPID-7012:
----------------------------------
I think there is no change required here for 6.1, at least for 0-8..0-10. Any
in-flight asynchronous transactions are completed by
{{ProtocolEngine#received}} before control returns to the IO layer. This will
constrain the amount of work to a maximum of a network buffer size (256 * 1024
bytes by default).
> Connections producing lots of non-transactional persistent messages can cause
> other transactions to be delayed/time out
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7012
> URL: https://issues.apache.org/jira/browse/QPID-7012
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> Work mixes that include
> * connection producing large numbers of persistent messages *without*
> transactions
> * transactional work
> may see timeouts in some situations.
> In the HA case, the non-transaction messages are sent to the replicas lazily,
> so all replicas may get behind. This means the a transaction will need to
> wait for the replicas catch up before its transaction completes.
> In the non-HA (and HA on the master), the commit related to the transactional
> work may queue behind the commit jobs related to the non-transactional work.
> This problem affects only publishes using unconfirmed publishes, currently
> the defect for AMQP 0-8..0-91 on in the Java Client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
