Sean Flanigan, I understand your point and agree that under some circumstances (custom JDBC wrappers, etc.), a warning might be useful during development. But in my opinion, there are more situations where JDBC drivers and connection pools cause the excessiveness. It's the usual balancing act, and here I think DEBUG is the most appropriate. If many others think otherwise, keep up the discussion.