]
Masafumi Miura moved JBEAP-14531 to MODCLUSTER-653:
---------------------------------------------------
Project: mod_cluster (was: JBoss Enterprise Application Platform)
Key: MODCLUSTER-653 (was: JBEAP-14531)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Core & Container Integration (Java)
(was: mod_cluster)
Affects Version/s: 1.3.7.Final
(was: 7.1.1.GA)
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
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 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.