Hello,
The reason that the actual delay is longer than the set value likely has to do with what is executed in other Threads while delaying, and how many Threads are running. If the other Threads are utilizing a lot of memory than this may cause Garbage Collection to run. If Garbage collection runs during the LoadTest, this can cause a delay to take much longer than expected. Unfortunately there isn't much we can do about this. I have tweaked a few things that should improve delay timing slightly, which will be available in the next nightly build (soapUI 3.5 beta only). The Garbage Collection related probelms still exist though.
Regards,
Dain
eviware.com