“A message going to a one-way send port is being suspended. Reason:The send port configuration corresponding to the message was not found. This usually happens when a send port was deleted while it still had some active messages”
This is a very ackward error that you can’t an answer in any of the microsoft documentations.
We found this error in our production system soon after the interface was redployed. We went crazy to think if the redeployment has deleted the send ports.
When we checked event log entries, we also found some SSO erros associated with this. So atleast this gave us a hint that the configuration information has not updated and the host instances thinks that the send ports is not available anymore.
To tackle this problem, we changed the send handler to run under different host instance and resumed the messages.
Hooray, it went through.
1. The error description that microsoft has given is not clear enough to resolve the problem.
2. Even after the host intances that were used for the interface was bounced back, the messages were not going through. So the SSO needs to be restarted for the host instance to work properly. But in production environment, we can’t do this. So this is a bug.