Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Reliable Messag... » Answers   (RSS)

Why Ordering is Ignored

Why doesn't validation catch when the two sides of a reliable connection disagree about whether the session is ordered? It doesn't actually matter to the sender whether the session is supposed to be ordered, and so it doesn't actually matter whether the

Silent Security Failures

I'm using reliable messaging and getting an exception that the reliable session has faulted. It's the first exception that I see so I don't know why the session faulted. How do I know what went wrong? Here's the full error message: The underlying secure

Sticky Sessions

How can I use reliable messaging together with a load balancer? The point of reliable messaging is to help ensure that messages get from one place to another. This means that the protocol notices when messages that were expected to be delivered go missing.

Session Lifetime on the Server

Why doesn't increasing the InactivityTimeout of a reliable session keep client connections alive for longer? When using a reliable session, there are two different inactivity timers that must be satisfied to keep the connection alive. If either inactivity

Socket Failures

What is the lifetime of a TCP session? The lifetime of the session object from a TCP transport channel lasts exactly as long as you own the underlying TCP connection. Once you give up ownership of the TCP connection, either by saying that you're done

Incompatible Addressing with Reliable Messaging

This was a bug that we found a few weeks before V1 shipped but it was not deemed severe enough to fix at the time. I know that one customer has hit this while experimenting and it's pretty easy to understand what's going wrong once you hear the details.
 
Page view tracker