[jboss-jira] [JBoss JIRA] (WFLY-13166) https connector / idletimeout / keep-alive settings

[Abdul Islam (Jira)]

     [ https://issues.redhat.com/browse/WFLY-13166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abdul Islam updated WFLY-13166:
-------------------------------
    Description: 
Hi,

We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings  at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. W



Thanks

  was:
Hi,

We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing gateway timeout 502 for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings  at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. W



Thanks



> https connector / idletimeout / keep-alive settings
> ---------------------------------------------------
>
>                 Key: WFLY-13166
>                 URL: https://issues.redhat.com/browse/WFLY-13166
>             Project: WildFly
>          Issue Type: Task
>            Reporter: Abdul Islam
>            Assignee: Brian Stansberry
>            Priority: Major
>
> Hi,
> We're using Wildlfy v15.0.1 and external traffic reaches Wildfly app servers via a load balancer, lately we are seeing 502 gateway timeout for certain calls. One of the recommendation from load balancer support team is to enable keep-alive settings  at the app server level to match the load balancer, we have a 15 min idle time out set on load balancer. It would be great if anyone has any insights or recommendations on this topic. W
> Thanks



--
This message was sent by Atlassian Jira
(v7.13.8#713008)