[
https://issues.apache.org/activemq/browse/AMQCPP-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQCPP-196.
---------------------------------
Resolution: Fixed
Resolved in trunk, new configuration parameters are documented on the Wiki
> Make the openwire connecter handle sending messages sync or async based on
> rules and settings
> ---------------------------------------------------------------------------------------------
>
> Key: AMQCPP-196
> URL: https://issues.apache.org/activemq/browse/AMQCPP-196
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: Openwire
> Affects Versions: 2.2.1
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 2.2.2
>
>
> The only messages that really require a synchronous send are persistant
> messages not in a transaction, so we should send the rest asynchronously. We
> should support flags for forcing always sync sends and also forcing async
> sends of persistant messages not in a transaction as well.
> We will need to also start monitoring the producer window size since messages
> will be going out async. This means we needs to somehow get close to the
> message sizes that the broker will be returning in the ProducerAck message.
> This will allow use to use better producer flow control for async sends.
> Currently all our sends are sync so we just depend on the broker for flow
> control, stalling on a send if a timeout is not set.
> This should result in a net performance increase for message that don't need
> to be sent synchronously.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
