You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/07 15:17:00 UTC
[jira] [Commented] (ARTEMIS-1978) AMQP sequencing errors can occur
when multi-frame deliveries are multiplexed on a session
[ https://issues.apache.org/jira/browse/ARTEMIS-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571824#comment-16571824 ]
ASF GitHub Bot commented on ARTEMIS-1978:
-----------------------------------------
GitHub user gemmellr opened a pull request:
https://github.com/apache/activemq-artemis/pull/2221
ARTEMIS-1978: update to proton-j 0.27.3 to resolve sequencing issues
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gemmellr/activemq-artemis delivery-multiplexing
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2221.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2221
----
commit b496cfc5c9a3d0878568b415d965ec51d049b3c7
Author: Robbie Gemmell <ro...@...>
Date: 2018-08-07T14:35:16Z
ARTEMIS-1978: update to proton-j 0.27.3 to resolve sequencing issues
Adds test exposing broker behaviour from issues stemming from PROTON-1892 and PROTON-1901
----
> AMQP sequencing errors can occur when multi-frame deliveries are multiplexed on a session
> -----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1978
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1978
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.6.2
> Reporter: Marcel Meulemans
> Priority: Major
> Fix For: 2.7.0
>
>
> Given a client that is subscribed to two queues and first queue has a large message that is transferred in multiple frames, a message in the second queue can/will get the same delivery id causing a sequencing error. The cause of the bug is in proton-j and has been reported and fixed: PROTON-1892
> This report is just for tracking the fix into Artemis.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)