Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Unresolved
Priority: Major
Fix Version/s: 8.1 Update 4
Affects Version/s: 8.1.0.GA
Component/s: None
Labels:
- needs-backport

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

8.1.z.GA
Git Pull Request:
https://github.com/wildfly/wildfly-proposals/pull/734, https://github.com/wildfly/wildfly-http-client/pull/282
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The socket options look to be completely unconfigurable as the socket options are static and unconfigurable in the WildflyHttpContext. Can we improve WildflyHttpContext so TCP_NODELAY (and possibly other options) is configurable and/or enabled by default?

Without TCP_NODELAY, latency concerns from WEJBHTTP-143 is made worse.

Follow up on ~~WEJBHTTP-144~~.

clones

WEJBHTTP-154 Support TCP_NODELAY in wildfly-config.xml

Pull Request Sent

depends on

JBEAP-31466 [GSS](8.1.z) WEJBHTTP-144 - Allow additional TCP configurations like TCP_NODELAY

is incorporated by

JBEAP-31468 (8.1.z) Upgrade WildFly Http Client from 2.1.3.Final-redhat-00001 to 2.1.4.Final

is related to

WEJBHTTP-144 Allow additional TCP configurations like TCP_NODELAY

Resolved

WEJBHTTP-143 Packet split of request in EJB over HTTP adds additional latency

Pull Request Sent

Assignee:: Jason Lee

Reporter:: Aaron Ogburn

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2025/11/14 5:07 PM

Updated:: 2025/11/21 9:58 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates