[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-653) mod_cluster DefaultMCMPHandler should handle "Connection: close" response header and close a connection
Radoslav Husar (JIRA)
issues at jboss.org
Mon Apr 16 09:31:00 EDT 2018
[ https://issues.jboss.org/browse/MODCLUSTER-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MODCLUSTER-653 started by Radoslav Husar.
-------------------------------------------------
> mod_cluster DefaultMCMPHandler should handle "Connection: close" response header and close a connection
> -------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-653
> URL: https://issues.jboss.org/browse/MODCLUSTER-653
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.3.7.Final
> Reporter: Masafumi Miura
> Assignee: Radoslav Husar
> Fix For: 1.4.0.Final, 2.0.0.Alpha1, 1.3.10.Final
>
>
> mod_cluster {{DefaultMCMPHandler#sendRequest()}} does not close a connection when Apache httpd closes a connection and responds to MCMP STATUS request with "{{Connection: close}}" response header. (As {{KeepAlive Off}} is set by default, Apache httpd closes a connection and responds to MCMP STATUS request with "{{Connection: close}}".) Therefore, CLOSE_WAIT connection remains every MCMP STATUS command.
> This CLOSE_WAIT connection will be cleaned when trying to send the next MCMP STATUS request, so there's no functional impact. And this is not a critical issue as neither connection leak nor file descriptor leak happens. However, it's better that mod_cluster handles the "{{Connection: close}}" response header and close a connection.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the mod_cluster-issues
mailing list