WCF Custom Transport Channel: Dispatcher does not invoke the Service Operation

Damir Dobric Posts

Next talks:



Follow me on Twitter: #ddobric




 I implemented one custom transport based on duplex-shape. Unfortunately, the transport was in some scenarios not able to route the message to wanted operation.

After intensive tracing and debugging I figured out that one message is not routed to the service if at least one of following is true:


  • The message is not well formed. In that case the service model creates the fault message. This can be the case when the message for example does not have a body at all, or the body is not serialized according to expected specification.
  • The action specified in the header does not match the operation which should be invoked.
  • The ‘To’ header of the message does not match the ListeningUri of the service.

The routing of the message is processed in the internal cWCF lass ImmutableDispatchRuntime in one of ProcessMessageN methods.

Posted Aug 06 2006, 11:04 PM by Damir Dobric
Filed under:


Damir Dobric Posts wrote Custom Channel and Message Delivering
on 04-04-2007 1:04

By implementing of the custom channel or by manipulating of the message in message inspectors (custom

developers.de is a .Net Community Blog powered by daenet GmbH.