Weeee! At least we know it only blows up if logging is enabled... ;-)
I'll have a look.
Clinton
On 10/9/06, Jeff Butler <
[EMAIL PROTECTED]> wrote:
Hi Clinton,It took me nearly forever to figure out what was different in my setup from the iBATIS build. I almost ended up fixing the problem, but I wanted to leave some of the fun for you! It ended up that I didn't need to commit any changes or new tests.Here's how to break it...1. Go into .../test/log4j.properties and enable logging on java.sql.Connection (just uncomment the 11th line).2. Run the build. You'll see two errors/failures. Both caused by "statement is closed" - the error I'm seeing in my test enviornment.Jeff Butler
On 10/7/06, Clinton Begin < [EMAIL PROTECTED]> wrote:The cache is transaction scope only, so size will never be a problem (unless someone is literally using THOUSANDS of different statements in a single transaction with THOUSANDS of threads.
Plus, arbitrarily expiring statements from the cache based on some size would probably kill the performance anyway, and trying to be smart about it would probably be too complex and would ultimately also kill performance. :-) So cache size configuration is a no go.
But disabling it completely is definitely an option. Just a global setting will do.
Cheers,
Clinton
