My business process uses Undercover Agent (UCA, the activity with the icon of an envelope) to accept the response from my testing client (a JAVA application, which sends automatical JSON response to the BPM process using BPM REST API).
For the purposes of measuring time, I want to run this process repeatedly, i. e., at least 150 times. About 15-30 consecutive iterations proceed normally, however, the next repetition "gets stuck" on this UCA. The Inspector in Process Designer claims that the problematic instance is in active state and "eternally" waits for the incoming response.
This line of SystemOut.log may (not) be relevant:
[9/4/13 22:07:37:443 CEST] 00000a0f wle W CWLLG0297W: The intermediate event with ID BpdEvent.1204214e-35e7-4b73-bf71-85f9d798ff5a can never receive a message from UCA UCA.7d0d96f1-9691-43af-81f5-b4fe1bc025cc because it is correlated on an invalid output parameter.
To sum up, many instances are perfectly okay yet there is always one that halts the whole time-measurement. What causes this behavior?