[
https://issues.apache.org/jira/browse/QPID-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-3659.
------------------------------------
Resolution: Fixed
Assignee: Rajith Attapattu
> Java client mishandles tcp_nodelay when specified as part of the broker URL
> ---------------------------------------------------------------------------
>
> Key: QPID-3659
> URL: https://issues.apache.org/jira/browse/QPID-3659
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.15
> Reporter: Kim van der Riet
> Assignee: Rajith Attapattu
>
> When tcp_nodelay is set as part of the broker's address, the performance of
> the client drops badly, no matter whether the value is set to 'true' or
> 'false'. I assume that the parameter is being mishandled and is tuning off
> the tcp_nodelay property (which is by default on) even when set to 'true'.
> amqp://guest:guest@/test?brokerlist='tcp://20.0.10.43?tcp_nodelay=true'
> returns serialised get-put cycles onto a single queue at the rate of 25/sec,
> but
> amqp://guest:guest@/test?brokerlist='tcp://20.0.10.43'
> returns 3017/sec under otherwise identical conditions.
> I assume that the lower performance figure is consistent with tcp_nodelay not
> being active in this test case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
