Monday, May 3, 2010

DBCP Pool Broken Pipe

What may look like a broken pipe may actually be a SQL Statement failure. I have found in the cases where SQL statements are incorrect will cause a Broken Pipe to throw. It can cause anything trying to connect using the connection ont that pool to throw an exception too.

Add Log4J and watch your SQL Statements. First check file descriptors before you get carried away with this, although this is pretty easy to do. Add logging to your exceptions so you can easily identify your errors.

What to check:
1. check OS Max file descriptors, this is usually the case
2. if you raised the file descriptors, you may have a bad SQL statement causing the error. Seeing the stack trace isn't always clear to determine which sql statement threw the event.

No comments:

Trying out the Dart Analysis Server

I wanted to see how the Dart Analysis Server was put together and worked. I started looking to see how I could wire it up and try out the co...