activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From davidmc <>
Subject Re: option wireFormat.tcpNoDelayEnabled=true seems to be ignored
Date Thu, 15 Feb 2007 05:52:06 GMT

Hello ActiveMQ devs,

I don't want to seem picky :( but 1 week has passed and still no feedback on
this TCP_NODELAY issue.
Finding that "wireFormat.tcpNoDelayEnabled" does not work but
"socket.tcpNoDelay" DOES work even if it is not documented, already helped 1
person...  see the last comment of Helmut at .

So, could you please update the documentation at or to point out that
one should use socket.tcpNoDelay=true to enable TCP_NODELAY in ActiveMQ
sockets (i.e. disable Nagle's Algorithm)?

Just edit the wiki to add something like... "At the moment
wireFormat.tcpNoDelayEnabled=true option does not work, please use
socket.tcpNoDelay=true instead" or whatever you want.

Also it shouldn't take much time to change the code to accept
wireFormat.tcpNoDelay as the documentation actually says... this is just an
option parsing / option forwarding problem.

If you don't at least document the socket.tcpNoDelay workaround, this can
lead people to believe that ActiveMQ performs bad in Linux - because with
Windows localhost sockets, this problem doesn't arise, unlike Linux sockets
- and people testing ActiveMQ on Linux may be disappointed.

Thanks in advance, regards,


davidmc wrote:
> At least in connection URL's used by clients, the option
> wireFormat.tcpNoDelayEnabled=true is ignored silently in versions 4.0,
> 4.1.0 and 4.2.0.
> So, you may have tried to disable Nagle's algorithm, to reduce latency for
> example, without noticing any effect...
> workaround: use socket.tcpNoDelay instead, for example:
> "tcp://localhost?socket.tcpNoDelay=true"
> Please see the issue I created at
> .
> Regards,
> David

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message