From the Java Language Specification 14.20.2.: If the catch block completes abruptly for reason R, then the finally block is executed. Then there is a choice: If the finally block completes normally, then the try statement completes abruptly for reason R. If the finally block completes abruptly for reason S, then the try statement completes … Read more
Basically, fs.readFileSync throws an error when a file is not found. This error is from the Error prototype and thrown using throw, hence the only way to catch is with a try / catch block: var fileContents; try { fileContents = fs.readFileSync(‘foo.bar’); } catch (err) { // Here you get the error when the file … Read more
PM2 First of all, I would highly recommend installing PM2 for Node.js. PM2 is really great at handling crash and monitoring Node apps as well as load balancing. PM2 immediately starts the Node app whenever it crashes, stops for any reason or even when server restarts. So, if someday even after managing our code, app … Read more
The big difference is that try…catch will swallow the exception, hiding the fact that an error occurred. try..finally will run your cleanup code and then the exception will keep going, to be handled by something that knows what to do with it.
PERFORMANCE: There is absolutely no performance difference in where the try/catch structures are placed. Internally, they are implemented as a code-range table in a structure that is created when the method is called. While the method is executing, the try/catch structures are completely out of the picture unless a throw occurs, then the location of … Read more
My exception-handling strategy is: To catch all unhandled exceptions by hooking to the Application.ThreadException event, then decide: For a UI application: to pop it to the user with an apology message (WinForms) For a Service or a Console application: log it to a file (service or console) Then I always enclose every piece of code … Read more
Usually empty try-catch is a bad idea because you are silently swallowing an error condition and then continuing execution. Occasionally this may be the right thing to do, but often it’s a sign that a developer saw an exception, didn’t know what to do about it, and so used an empty catch to silence the … Read more
try has almost no expense at all. Instead of doing the work of setting up the try at runtime, the code’s metadata is structured at compile time such that when an exception is thrown, it now does a relatively expensive operation of walking up the stack and seeing if any try blocks exist that would … Read more
I prefer the second one. May as well trap errors relating to the creation of the object as well.
You need to enclose your try-catch inside a while loop like this: – int count = 0; int maxTries = 3; while(true) { try { // Some Code // break out of loop, or return, on success } catch (SomeException e) { // handle exception if (++count == maxTries) throw e; } } I have … Read more