[
https://issues.jboss.org/browse/WFCORE-1132?page=com.atlassian.jira.plugi...
]
Jason Greene commented on WFCORE-1132:
--------------------------------------
[~andy.miller] netty-xnio is only used for JMS over HTTP Upgrade, where undertow hands off
the connection. Direct connections are pure netty over NIO.
I did test the JMS quick start, which uses HTTP, and it didn't set the setting.
Last night I decompiled all jars in wildfly, and searched the symbol table to
Options.SEND/RECEIVE_BUFFER and didn't see anything that would cause it, other than
config, but I need to double check the parsers, to see if there is some funky condition
where they pipe in a management setting.
Only set socket send and receive buffer sizes if it is in the
Remoting subsystem configuration
----------------------------------------------------------------------------------------------
Key: WFCORE-1132
URL:
https://issues.jboss.org/browse/WFCORE-1132
Project: WildFly Core
Issue Type: Bug
Affects Versions: 2.0.1.Final
Reporter: Andrig Miller
Priority: Blocker
Fix For: 2.0.2.Final (EAP 7)
Original report:
{quote}
In our testing of Wildfy 10 CR4, in the performance lab, we found that one of the
differences between EAP 6.4.x and Wildfly 10 was that EAP does not set the socket send and
receive buffers. We changed the configuration of Wildfly (Undertow) to remove the buffer
parameters from the configuration, and we found that the buffer sizes were still be set to
8k. We hacked XNIO to comment out the setting of these parameters, and latency improved
quite a bit.
So, we need a permanent fix so that the socket send and receive buffers are only set, if
they are specified in the configuration.
{quote}
This applies to the Remoting subsystem configuration, versions 2.0 and onwards, and also
possibly to Undertow, though that subsystem does not appear to use default values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)