This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have a standalone java enviornment with robust exception handling and the application is well tested.
But some times the process flow is not behaving the way it is expected.
Thus I would want to keep track of anything abnormal that might be happening by looking at the log files. I am thinking that log4j configuration might not help me to log the occurence of the java.lang.Error subclasses.
Similar to the .out files in weblogic enviornment which logs everything that happens in the JVM including the occurence of any java.lang.Error (like stackoverflow/outofmemoryerror), is there a way to capture such errors when occured in a standalone/non-J2EE enviornment?