Friday, December 9, 2016

Operation element is not declared

We were doing load testing of one of the interfaces which sends message to destination using WCF-WebHttp adapter configured dynamically in orchestration. Not much load - just 100 messages in few minutes, but found that 5 of the messages got suspended.

This was bit confusing as until now all went fine in all the env and no suspended messages, except here in Performance env.

Operation element is not declared


Why it happened

After looking out for this error, found that this is known issue with WCF-WebHTTP adapter along with Dynamic send Port when under load.

What to do

You need to apply the cumulative update provided by Microsoft, which can be found at following link:

No comments:

Post a Comment