Well you could try ...
- IBM's ConTest to instrument your code before you run your tests. Though I must admit I have coded some non JSR 133 compliant code that got away with it that still passed.
- or I've been playing with the idea of running tests with terracotta (
java on clustered PC's) as it requires no libs just config and you can state the bits of memory you expect shared and they should then be shared cross PCs with memory going over the wires only on hitting memory barriers etc. I'm still not sure how practical this is as you still have to force threads via it onto differing PC's, currently all threads would start up on all PC's , you can program round this with things like singletons but I didn't want any special code for the test , I'm sure they could write a very nice testing tool, maybe use annotation to suggest to terracota what to do with the threads in a test scenario.
"Eagles may soar but weasels don't get sucked into jet engines" SCJP 1.6, SCWCD 1.4, SCJD 1.5,SCBCD 5