[ https://issues.jboss.org/browse/MODCLUSTER-356?page=com.atlassian.jira.pl... ] Weinan Li commented on MODCLUSTER-356: -------------------------------------- Yeah if I restart httpd/EAP sometimes it will throw: {code} Error null sending STATUS command to min/10.0.1.13:10001, configuration will be reset: null {code} And this just happen during server restart to me. The httpd crashing stopped after I've upgrade mod_cluster to 1.2.6.Final in httpd. No crashing anymore, and no error log from both EAP and httpd sides, and node could be seen correctly from '/mod_cluster-manager'. From wireshark analyse the CPING/CPONG of AJP port between EAP/httpd are fine. But the "<title>503 Service Temporarily Unavailable</title>" still exists. The node is not serving. I've also tried to upgrade mod_cluster in EAP side also to 1.2.6.Final and the problem still there. Not sure where the problem could be. Because Wireshark doesn't understand the MCMP in 10001 port, so it's hard for me to see if there are any problems. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira