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.
In I/O code it's not a good idea to ignore exceptions. In both catch blocks you should at least print a warning, or -even better- the stack trace of the exception, or you'll never know that were was a problem.
Also, when posting code of any length, please UseCodeTags.