Catching Errors: opinions needed

Question

Under what conditions should a program try to catch Errors (not Exceptions) ? The docs for the Error class read:
"An Error is a subclass of Throwable that indicates serious problems that a reasonable application should not try to catch."
However, nothing enforces the fact that I should not try to catch an Error. I can catch a StackOverFlowError, ExceptionInInitializerError, etc. just as I would catch any Exception class.
Everything I have read talks plenty about Exception handling, but basically nothing about Error handling.
My questions are: 1) Why doesn't the JVM prevent me from catching Errors? 2) Under what conditions should I try to catch Errors? 3) What are good practices for handling Errors?

Answer 1

My questions are: 1) Why doesn't the JVM prevent me from catching Errors? In case you need to catch them.
2) Under what conditions should I try to catch Errors?When you want to perform an action when a specific error occurs.
An action I perform is to shutdown my server when an OutOfMemoryError or StackOverflowError occurs. This is required as an Error only results in the end of the thread which threw it. The other threads can keep running, leaving a running but unless application, like a zombie. Under this condition, if the application is not working it should shutdown. e.g. System.exit();
3) What are good practices for handling Errors?When you catch an erro you should rethrow it. (I don't always, but this is considered good practice)