Outside of using a decent framework, a lot of J2EE applications still handle their own DBIO. And just like memory resource leaks are a problem in C++, database resource leaks are a problem in virtually every J2EE application I’ve worked on.

But what do you do? You’ve got a legacy code base of several hundred thousand lines of code. Much of it written by (less than ideal) coders who have since left the project. There isn’t the money to fix every leak, even if you could find them all. And don’t even mention switching to a better framework. Just keep patching the worst offenders, right?

(more…)