Article:		Three Rules for Effective Exception Handling
Subject:		Not, reasonable application SHOULD catch it
Date:		2003-12-05 11:16:04
From:		krage
Response to: Catching Errors
... particularly mission critical. OutOfMemoryError often happens when the application is trying to allocate a lot of objects or instance in deserialization, but the whole process can be rolled back by the releasing the created objects - just set referenrce to null and gc will help you to recover. Besides, you still can do some other things like notifing your sa.