Bug 753238
| Summary: | Java messaging client now enables TCP_NODELAY by default | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Justin Ross <jross> |
| Component: | Release_Notes | Assignee: | Tomas Capek <tcapek> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Zdenek Kraus <zkraus> |
| Severity: | low | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.0 | CC: | iboverma, lbrindle, rattapat+nobody, zkraus |
| Target Milestone: | 2.1.2 | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-05-24 15:37:17 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 761186 | ||
| Bug Blocks: | 755648 | ||
| Deadline: | 2011-12-09 | ||
|
Description
Justin Ross
2011-11-11 17:03:07 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) This bug can be done for 2.2, if source content is received before 9 December. LKB No content has been received. Nacking. LKB 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
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.
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 It's correct. -> VERIFIED |