[
https://issues.apache.org/jira/browse/AMQNET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krzysztof Porebski closed AMQNET-602.
-------------------------------------
Resolution: Fixed
> Performance issue with brokers that respect batchable flag
> ----------------------------------------------------------
>
> Key: AMQNET-602
> URL: https://issues.apache.org/jira/browse/AMQNET-602
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: AMQP, NMS
> Affects Versions: 1.8.0
> Reporter: Krzysztof Porebski
> Priority: Major
> Time Spent: 3h
> Remaining Estimate: 0h
>
> MessageProducer rate are 1 msg/sec on brokers that respect the batchable flag
> for amqp transfers. This has been a long standing issue with amqpnetlite
> until it was fixed for synchronous sends, version 2.1.8. The provider
> AmqpProducer uses async sends with ManualResetEvent to block. This is bad in
> term of amqp protocol as the transfer sent as batchable indicating to the
> broker that disposition should not be sent right away so it waits however the
> client is also waiting for a response leading to terrible message rates.
> Amqpnetlite fixed this issue at least for synchronous sends from a sender
> link where the batchable flag is set to false when a send is synchronous
> however that means that AmqpProducer must use a different send (see
> senderLink.send(msg) and senderLink.send(msg, timeout)) method then its
> currently using.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
