Bug 753238 - Java messaging client now enables TCP_NODELAY by default
Summary: Java messaging client now enables TCP_NODELAY by default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Deadline: 2011-12-09
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Release_Notes
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: 2.1.2
: ---
Assignee: Tomas Capek
QA Contact: Zdenek Kraus
URL:
Whiteboard:
Depends On: 761186
Blocks: 755648
TreeView+ depends on / blocked
 
Reported: 2011-11-11 17:03 UTC by Justin Ross
Modified: 2012-05-24 15:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The JMS client now sets TCP_NODELAY to 'true' by default as it shows an improvement in many general cases. If there is a configuration error (error in connection URL etc), the client will still default to true. For high throughput cases it is worthwhile to experiment by turning off TCP_NODELAY. Please refer to, 3.6.�Configuring the JMS Client and 3.2.2.�Connection URLs in the programming guide on how to configure this property.
Clone Of:
Environment:
Last Closed: 2012-05-24 15:37:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Justin Ross 2011-11-11 17:03:07 UTC 
Rajith will expand.
Comment 1 Douglas Silas 2011-11-21 17:59:25 UTC 
Hi Rajith, do you have a Release Note for this issue? And this should go into the 2.1 Release Notes, right?

Thanks,

Silas (and Tomas)
Comment 2 Lana Brindley 2011-12-05 21:45:46 UTC 
This bug can be done for 2.2, if source content is received before 9 December.

LKB
Comment 4 Lana Brindley 2012-01-03 19:59:30 UTC 
No content has been received. Nacking.

LKB
Comment 5 Rajith Attapattu 2012-01-23 21:11:24 UTC 
Lana, since this is not a bug fix I was wondering if I should be using a different format than CCFR ?

Let me know and I will add the details ASAP.

Rajith
Comment 7 Rajith Attapattu 2012-01-25 14:55:38 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The JMS client now sets TCP_NODELAY to 'true' by default as it shows an improvement in many general cases. If there is a configuration error (error in connection URL etc), the client will still default to true.

For high throughput cases it is worthwhile to experiment by turning off TCP_NODELAY. Please refer to, 3.6.�Configuring the JMS Client and 3.2.2.�Connection URLs in the programming guide on how to configure this property.
Comment 8 Tomas Capek 2012-03-22 13:05:08 UTC 
Added to: Red_Hat_Enterprise_MRG-MRG_Release_Notes-2-en-US-2-21

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2/html/MRG_Release_Notes/chap-MRG_Release_Notes-RHM.html#Red_Hat_Messaging_2.1_Release
Comment 9 Zdenek Kraus 2012-03-22 20:43:26 UTC 
It's correct. 

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