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.
"Show Some Effort" includes figuring out where and why exceptions happen. For example, NullPointerException happens if an object is null and your code tries to invoke a method on it. So you need to figure out which object is null, and then take steps to ensure that either a) it is not null when you invoke a method on it, or b) check for null before you invoke a method. Just posting the stack trace without anything else really serves no purpose.
What concrete steps have you taken to figure this out?
Also note that it's bad form to use the same discussion thread for two different questions (which these are, seeing that it's two different exceptions).