activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Resolved: (AMQNET-189) ActiveMQ client doesn't properly implement producer flow control
Date Thu, 24 Sep 2009 20:35:52 GMT


Timothy Bish resolved AMQNET-189.

    Resolution: Fixed

Fixed in trunk.

* Client now implements a client side Producer Window for local flow control when configured.
* The Connection now supports the AsyncSend and AlwaysSyncSend options correctly.  
* Non-persistent messages are sent asynchronously unless always sync sends are enabled.
* Messages in a Transaction are sent Asynchronously.
* Messages are copied on send now unless the CopyMessageOnSend option is set to false, this
allows message object to be reused in the client code while the sent message is still in-flight.

> ActiveMQ client doesn't properly implement producer flow control
> ----------------------------------------------------------------
>                 Key: AMQNET-189
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ
>    Affects Versions: 1.1.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 1.2.0
> The NMS.ActiveMQ client doesn't deal with producer flow control correctly and needs to
be enhanced.
> Changes Needed:
> * Process the ProducerAck message
> * Message sends only need to be sync when the message is Persistent or AlwaysSyncSend
is enabled.
> * Local Memory Tracking should be implemented when the Producer is assigned to control
its own overhead and the producer should wait for the Broker to ack its sent messages before
it continues to send.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message