[
https://issues.apache.org/jira/browse/ARTEMIS-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573722#comment-16573722
]
ASF subversion and git services commented on ARTEMIS-1978:
----------------------------------------------------------
Commit 7214d56581cbd5082b9bfddfc57f95e946d2433f in activemq-artemis's branch
refs/heads/2.6.x from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=7214d56 ]
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
(cherry picked from commit b0c65ba2dd5b7d1bc0dc75f9370c52da49f39bbf)
> 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
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 2.7.0, 2.6.3
>
>
> 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)
