Closed ljack closed 7 years ago
I would have to look into this. Cannot see an obvious reason for the delay. What OS is running Wildfly?
Not getting the slowness. Can you provide a little more detail on the environment. I used a standalone Windows server machine for everything.
Windows 6.3.9500 / Windows Server 2012 R2. IIS 8.5, IIS and WildFly both in the same machine. IIS is configured to do "Automatic Integrated Windows Login" with AD.
BonCodeAJP13.settings:
<Settings>
<Server>localhost</Server>
<Port>8009</Port>
<EnableRemoteAdmin>False</EnableRemoteAdmin>
<EnableHeaderDataSupport>True</EnableHeaderDataSupport>
<ForceSecureSession>False</ForceSecureSession>
<AllowEmptyHeaders>True</AllowEmptyHeaders>
<EnableHTTPStatusCodes>True</EnableHTTPStatusCodes>
<MaxConnections>0</MaxConnections>
<WriteTimeOut>2000</WriteTimeOut>
<LogLevel>1</LogLevel>
<PacketSize>16384</PacketSize>
<LogDir>C:\inetpub\logs\LogFiles\BonCode</LogDir>
</Settings>
Ah,
It seems the slowdown was caused because we're using
Hi, We upgraded our system from JBoss 4.2.3 to Wildfly 10.1.Final. After the upgrade we noticed that communications through IIS->Boncode->Wildfly takes minimum of 1 seconds for every request. Even request for resources that don't exist. If we communicate directely to Wildfly (port 8080) the response time for on existing resource it 32ms.
Wildfly has a large list of configurable parameters for network IO (https://docs.jboss.org/author/display/WFLY10/Undertow+subsystem+configuration).
Any advice?