Our configuration is kind of not recommended, but we are seeing a lot of mongodb connections issues (not the actual issue).
Sometimes this does fall into an uncaught exception where the application is in an unstable state and normally we expect the application to terminate.
We are not hosting in meteor.com, but another cloud provider and hosting this as a standard node application, at the moment our strategy is to catch uncaughtException and then process.exit(1).
What we are seeing is this does not terminate the application as we expect (the node.exe PID remains).
When this fails the application becomes unresponsive.
What do you recommend as best practice to ensure the application remains/restarts cleanly
We are using meteor 220.127.116.11 and node 0.10.41
Thanks for your trouble/advice in advance.