Stress Test using em console in 11g results in lesser number of instances

Question

Hi All,
We are doing Stress/Load testing using em console in SOA Suite 11g. The problem we are encountering is, em fails to create as many instances as it should. Under "Additional Test Options", we check the "Enable Stress Test" checkbox and give different values for following parameters:
Concurrent Threads     50
Loops per Thread     20
Delay in Milliseconds     1000
But instead of creating 1000 instances of this composite, em console create only 998 and fails to create 2 instances without giving any error in console logs or server logs.
Similarly, with below setting:
Concurrent Threads     50
Loops per Thread     40
Delay in Milliseconds     1000
Instead of creating 2000 instances it creates only 1991 and 9 instances fail without any error. Is this a known bug or we are missing something here? Any pointers will be helpful.
Thanks,
Akash

Answer 1

In case you have multiple instances running, whereas any instance has an unique value started as correlation, when the engine receives the messages for the intermediate receive operation it will be routed without problems to the right instance. In this case, it is not a problem if the engine creates a new composite instance for the intermediate messages.
We have this situation in Production without any problem.
Anyway should be simple to simulate the same situation in your development environment to make sure it works well in your scenario.
Regards
Luis Fernando Heckler