I've been working a bit today on making sure the .NET client handles undelivered messages gracefully (right now it doesn't quite do it), and making sure that the returned message is properly handled and the correct exception is notified through the connection (though from an API point of view, I think this is horrendous, but that's a different story).
As part of this, I've added the proper exceptions, handled bounced messages in the channel and I'm fixing the UnderliverableTest test in Qpid.Client.Tests, which pretty much didn't work (it didn't test anything as it was). So far, I've got everything working pretty nicely, except for underliverable messages sent to a topic exchange. I've checked everything, and indeed the java broker sees the message and the debug logs show it indeed recognizes it as undeliverable. However, it never sends a Basic-Return frame back to the client notifying it of the problem, like it happens with the direct and header exchanges. (I've verified traffic with a protocol analyzer, btw, so I'm sure the frame is not sent over the network) So the question would be: Is this expected for a topic exchange? Or am I just hitting a problem with the java broker? Any ideas? Tomas Restrepo http://www.winterdom.com/weblog/
