activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Why CloseAsync for STOMP transport connector?
Date Tue, 09 Apr 2013 20:19:10 GMT
for openwire users, where connections are typically long lived or
pooled, getting a fast exit, so a fast return from a call to
connection.close can be important.
So the broker can respond before the socket is closed with the default config.

stomp use cases tend to open/close connections for each request or
just open and die, and asyncClose can cause excessive fd usage on the
broker.

So what you need dependes on your use case and what is important.

On 9 April 2013 21:11, Paul Gale <paul.n.gale@gmail.com> wrote:
> Anyone have any thoughts on this?
>
> Thanks,
> Paul
>
>
> On Mon, Apr 8, 2013 at 6:07 PM, Paul Gale <paul.n.gale@gmail.com> wrote:
>
>> Hi,
>>
>> I was wondering why all the canned examples for activemq.xml one finds the
>> STOMP transport connector is nearly always configured with a transport
>> option of 'closeAsync=false'?
>>
>> Why is that?
>>
>> I read in the mail list archive the following:
>>
>> "... closeAsync=false can help reduce the number of open sockets if the
>> broker is busy at the cost of delaying the close response to the client."
>>
>> Assuming that's true why wouldn't one configure ALL other transport
>> connectors the same way?
>>
>> Thanks,
>> Paul
>>



-- 
http://redhat.com
http://blog.garytully.com

Mime
View raw message