Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Subject: Re: NMS.ActiveMQ.Producer deal with OnProducerAck
To: dev@activemq.apache.org
References: <1490000826211-4723881.post@n4.nabble.com>
From: Timothy Bish <tabish121@gmail.com>
Message-ID: <91d36cbc-5aa0-a554-f41f-f4293cbd7500@gmail.com>
Date: Mon, 20 Mar 2017 10:50:17 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <1490000826211-4723881.post@n4.nabble.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Mon, 20 Mar 2017 14:50:30 -0000

The producer window size bits of NMS.ActiveMQ were not very well tested 
so it could be there's a bug.  There is not access to the outside for 
the events that are part of this exchange so nothing you can do on your 
side.  If you want to debug and provide a fix and some tests we are 
happy to accept contributions.

On 03/20/2017 05:07 AM, xinchangan wrote:
> I am using NMS.ActiveMQ packages to send byte stream through a Queue with
> asynchronous and non-persistent mode. I have set ProducerWindowSize to keep
> the producer from occupying too much memory on the side of broker. But It
> seems the ProducerWindowSize +ProducerFlowControl have no any effect on the
> usage of my broker's memory and make the ActiveMQ halt everytime.
>
> Can I capture and deal with the notification  from the broker relevant to
> the excess of ProducerWindowSize? In fact I can't find a proper entry to get
> into OnProducerAck using NMS IMessageProducer interface. Are there any other
> solutions in the .net environment to cope with this issue?
>
> Thanks.
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/NMS-ActiveMQ-Producer-deal-with-OnProducerAck-tp4723881.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>


-- 
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/