Skip to main content

Service Bus Topics - Define custom rules for messages that don’t respect any rule defined in a topic

In one of my older post I tacked about how we can define filters for each subscriber of a Service Bus Topics. We saw how we can filter messages for a subscriber based on some rules that are defined using FilterExpression:
RuleDescription ruleDescription = new RuleDescription()


    Action = new SqlRuleAction("set isValid= false"),

    Filter = new SqlFilter("value = 10");






var subscription = namespaceManager.CreateSubscription(


    " thirdSubscription");


Using these rules is quite simple to define custom rules for the messages from a topic. But what about messages that don’t respect any rules defined in our topic? How we can detect these messages and define a custom rule for them. In a perfect word we can control the messages that arrive in our topic, but in a distributed system these thing doesn’t happen all the time.
For this cased we can use “MatchNoneFilterExpression” that will route to our topic all the messages that were not consumed by our subscribers. For example in our example we only consume messages that have the value equal with 10. What about the rest of the messages? Of course we can define a rule for values that are not equal with 10, but if we have more subscribes with different rules it will complicated to define the non-true rules for all the subscribers.
 RuleDescription notConsumedMessagesRule = new RuleDescription()


     FilterAction = new SqlFilterAction(“set isNotConsumed = true;”),

     FilterExpression = new MatchNoneFilterExpression()


In the above example our rule adds a property named “isNotConsumed” and set the value to true. Based on this rule we will able to route this messages to a specific subscriber.
In the same way we have another filter expression that is used when we want to define a rule for the messages that match all the filter expression from all our rules – MatchAllFilterExpression.
RuleDescription matchAllRule = new RuleDescription()
     FilterAction = new SqlFilterAction(“set matchAll = true;”),
     FilterExpression = new MatchAllFilterExpression()

Using this filter expression we can define custom rules for messages that didn’t respect any defined rule or messages that respect all the rules from our topic. In the end I want to enumerate the filter expression that can be used in this moment:
  • CorrelationFilterExpression
  • MatchNoneFilterExpression
  • MatchAllFilterExpression
  • SqlFilterExpression


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.