Does not know that the socket is closed by the ejabberd host

[jfjalburquerque]

When ejabberd host closes the socket of the service, the service does not know that this socket is closed.

[manuel-rubio]

Is it possible to reproduce the socket down? If I go to the shell and perform an exit/2 call for the service process (it should crash the socket resource too), the wrong happens?

[jfjalburquerque]

We could reproduce it closing the traffic for the service socket in the ejabberd host, after some time, (the test was with 30 min) we opened the traffic again, and then happen the issue, the service did not do anything. 503 error, and the service have not logs after that.

[manuel-rubio]

I was trying to... yes happens too when you kill the ejabberd_service related to the connection :-( ... no tcp_closed is sent to the process or the process controlling the connection is not in the ecomponent part... time to search in exmpp code :-S