Just noticed this strange behaviour on `deployment-restbase0x`: when a call to Parsoid results in `ECONNREFUSED`, RESTBase exists cleanly:
```
root@deployment-restbase02:/# systemctl status restbase
● restbase.service - LSB: REST storage API and backend orchestration layer
Loaded: loaded (/etc/init.d/restbase)
Active: active (exited) since Mon 2015-05-18 08:47:26 UTC; 37min ago
Process: 11558 ExecStart=/etc/init.d/restbase start (code=exited, status=0/SUCCESS)
```
What makes it really peculiar is the fact that if RESTBase is started manually (even as the //restbase// user), such thing does not occur, i.e. RESTBase keeps on running.
In both cases RESTBase returns the appropriate error JSON, which points to the fact that the exit occurs after closing the client connection.
Needs further investigation.