Basically, the program runs those commands over and over and over again. At some point the derby thread starts to spin.
Perhaps you are just giving your system more work than it can handle.
It sounds like you have some sort of a benchmark in place, and you are running it, looking for problems (which is a great technique!). If so, can you configure your benchmark so that you can adjust the "scale" factor in some fashion? Then start with a relatively small scale, verify that your system is healthy at that level, and then begin ratcheting up the scale until you start to see trouble. thanks, bryan
