[
https://issues.apache.org/jira/browse/AMQNET-718?focusedWorklogId=609842&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-609842
]
ASF GitHub Bot logged work on AMQNET-718:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Jun/21 17:42
Start Date: 10/Jun/21 17:42
Worklog Time Spent: 10m
Work Description: Havret commented on pull request #67:
URL: https://github.com/apache/activemq-nms-amqp/pull/67#issuecomment-858830340
@michaelandrepearce How should I configure broker to check this?
```
<address-settings>
<address-setting match="exampleQueue">
<max-size-bytes>100000</max-size-bytes>
<address-full-policy>BLOCK</address-full-policy>
</address-setting>
</address-settings>
```
Does `max-size-bytes` represents the number of messages for AMQP and the
number of bytes for core? Docs are pretty opaque in that matter.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 609842)
Time Spent: 20m (was: 10m)
> Inflight messages are not cancelled after timeout
> -------------------------------------------------
>
> Key: AMQNET-718
> URL: https://issues.apache.org/jira/browse/AMQNET-718
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: AMQP, NMS
> Affects Versions: AMQP-1.8.1, AMQP-2.0.0
> Reporter: Krzysztof Porębski
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Inflight messages are not cancelled in case of timeout. It may results in
> duplicates, when library used with producer control flow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
