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 subversion and git services (Jira)" <ji...@apache.org> on 2019/08/30 09:16:00 UTC
[jira] [Commented] (AMQNET-608) Provider shouldn't sent transfer
frames as settled when sender settled mode is unsettled
[ https://issues.apache.org/jira/browse/AMQNET-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919358#comment-16919358 ]
ASF subversion and git services commented on AMQNET-608:
--------------------------------------------------------
Commit 25ec0aadf9fcc3c1fc08b5b5ade9480d579f1c77 in activemq-nms-amqp's branch refs/heads/master from Michael André Pearce
[ https://gitbox.apache.org/repos/asf?p=activemq-nms-amqp.git;h=25ec0aa ]
Merge pull request #23 from Havret/transfer_settled_flag
AMQNET-608: Provider shouldn't sent transfer frames as settled
> Provider shouldn't sent transfer frames as settled when sender settled mode is unsettled
> ----------------------------------------------------------------------------------------
>
> Key: AMQNET-608
> URL: https://issues.apache.org/jira/browse/AMQNET-608
> Project: ActiveMQ .Net
> Issue Type: Bug
> Reporter: Krzysztof Porebski
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Amqp provider sends transfer frames on sender link as settled even when the sender settled mode is Unsettled (this is currently hard-coded value). This is against amqp spec. There is at least one broker that detaches the sender link when a non-persistent(settled) message is sent.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)