If it sounds stupid, then it probably is. Lazy vals work fine. One thing to have in mind is that a lazy val is null, it will be reevaluated again (the first thing that tripped me).
The problem is that I relied on findMessages working correctly. It didn't. Unfortunately the changes from access pools made it to always hit the DB and not try the cache. I've fixed it now. (tests, tests, tests) As a result, ESME is now as fast as we remember it from the beginning.
