Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 453417 - Allow tcp-nodelay to be set on server side of socket also
Summary: Allow tcp-nodelay to be set on server side of socket also
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: 1.0.1
: ---
Assignee: Gordon Sim
QA Contact: Kim van der Riet
Depends On:
Blocks: 459251
TreeView+ depends on / blocked
Reported: 2008-06-30 14:34 UTC by Gordon Sim
Modified: 2008-10-06 19:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-10-06 19:09:00 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0640 normal SHIPPED_LIVE Red Hat Enterprise MRG bug fix and enhancement update 2008-10-06 19:08:07 UTC

Description Gordon Sim 2008-06-30 14:34:32 UTC
Client currently allows tcp-nodelay to be set but that will only affect
client->broker traffic. For broker->client need to allow a client connection to
request that the broker set tcp-nodelay on its side of the socket also.

Comment 1 Gordon Sim 2008-08-05 17:07:16 UTC
Added in r.682791 (trunk) and r.682785 (qpid.0-10).

Comment 2 Gordon Sim 2008-08-15 08:04:35 UTC
Broker now has new --tcp-nodelay option to turn this feature on.

Comment 4 Jeff Needle 2008-09-16 12:04:28 UTC
This works as expected.

Comment 6 errata-xmlrpc 2008-10-06 19:09:00 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.