Skip to content
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.

Handle connexion problem with application #184

Closed
clochix opened this issue Oct 2, 2015 · 3 comments
Closed

Handle connexion problem with application #184

clochix opened this issue Oct 2, 2015 · 3 comments
Labels

Comments

@clochix
Copy link
Contributor

clochix commented Oct 2, 2015

Some time, the application is running but the connexion with it is lost, for an unknown reason (ECONNRESET). It may be reseted only for a single request, or for every following request. So the user get a 504 error, while the application is running.

Maybe could we add to the error page an action to try to restart the application ?

@clochix
Copy link
Contributor Author

clochix commented Oct 5, 2015

In fact, this happens when connections between proxy and the application are not closed cleanly. They stay in CLOSE_WAIT state. By default, Node only allows five concurrent connections to the same origin, so when we reach this limit, the proxy become unable to communicate with the application, and the only solution seems to be to restart the proxy (restarting the application itself seems useless).

@nono
Copy link
Member

nono commented Feb 4, 2016

See #235 and #238

@frankrousseau
Copy link
Contributor

@clochix reopen this issue if the problem persists.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants