Hah!! I wish these restrictions would pop up on my face rather than
having to discover them in the hard way :)
Dale many thanks for the clarification! Could this restriction be
overcome? maybe finding a way to pair the requests, maybe using a
request id in the Session ... can I make an improvement request perhaps
also work on it?
Best regards,
Giovanni
Dale Newfield wrote:
Giovanni Azua wrote:
The race-condition happens only because my simulation process uses the
execAndWait interceptor
The execAndWait interceptor has a restriction that it can only support a
single long running task per action name per session. It is this
restriction that allows follow-up requests to be paired with the
appropriate long running task.
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
