[JBoss JIRA] (WFLY-11691) Default no-request-timeout value on HTTP(s) listeners seems to be causing unexpected timeouts
by jaikiran pai (Jira)
jaikiran pai created WFLY-11691:
-----------------------------------
Summary: Default no-request-timeout value on HTTP(s) listeners seems to be causing unexpected timeouts
Key: WFLY-11691
URL: https://issues.jboss.org/browse/WFLY-11691
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 15.0.1.Final, 14.0.1.Final
Reporter: jaikiran pai
Assignee: Stuart Douglas
More than one users[1][2] have reported that they are seeing odd timeout issues with HTTP(S) calls in their applications. Based on the discussion in those threads, I believe there are 2 issues here, one in Undertow and one in WildFly.
In Undertow, I believe there's a bug which when using HTTP 1.1, in some cases, ends up marking an in-progress request as timed out (based on the value set for no-request-timeout). Thread[1] has more details on how to reproduce such a case, but like I note in that thread, I don't think the cipher suites is what's causing this. I haven't found the time to create a simpler reproducible application for that one yet and I haven't yet created a Undertow JIRA for it.
In WildFly, I think the default value of 60 seconds for no-request-timeout on the HTTP(s) listeners, is arbitrary and even too low. IMO, this probably should default to -1 (i.e. no specific timeout) and let the users decide what value makes sense in their setup.
[1] https://developer.jboss.org/thread/279379
[2] https://developer.jboss.org/thread/279261
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months
[JBoss JIRA] (WFLY-11690) Upgrade target XML namespace for Galleon packages from 1.0 to 2.0
by Alexey Loubyansky (Jira)
Alexey Loubyansky created WFLY-11690:
----------------------------------------
Summary: Upgrade target XML namespace for Galleon packages from 1.0 to 2.0
Key: WFLY-11690
URL: https://issues.jboss.org/browse/WFLY-11690
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
This is not very critical but I'd like to upgrade WildFly Core and WildFly Galleon packages to the latest schema to make sure the upcoming releases are supported longer by future Galleon releases, in case I decide to remove the package schema 1.0 from Galleon.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months
[JBoss JIRA] (WFCORE-4321) Upgrade target XML namespace for Galleon packages from 1.0 to 2.0
by Alexey Loubyansky (Jira)
Alexey Loubyansky created WFCORE-4321:
-----------------------------------------
Summary: Upgrade target XML namespace for Galleon packages from 1.0 to 2.0
Key: WFCORE-4321
URL: https://issues.jboss.org/browse/WFCORE-4321
Project: WildFly Core
Issue Type: Task
Components: Build System
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
This is not very critical but I'd like to upgrade WildFly Core and WildFly Galleon packages to the latest schema to make sure the upcoming releases are supported longer by future Galleon releases, in case I decide to remove the package schema 1.0 from Galleon.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 8 months