Skip to main content

Message queue - cum sa oprim consumul de message dintr-un queue

Pornim de la următorul caz:
Avem o aplicatie ce ruleaza 24h pe zi, 7 zile pe saptamana. Aceasta consuma mesaje din mai multe queue. Pentru a putea asculta la queue avem următorul cod:
System.Messaging.MessageQueue msmq = new MessageQueue(".\\private$\\exemplu");
msmq .ReceiveCompleted += m_ReceiveCompleted;
msmq .BeginReceive();
void m_ReceiveCompleted(object sender, ReceiveCompletedEventArgs e)

MessageQueue msmq = (MessageQueue) sender;
Intr-un anumit moment, dorim sa oprim consumul de mesaje din queue. Pentru acest lucru apelam
Dar avem o surpriza. Mesajele sunt în continuare consuma de către aplicație. Orice am face sau apela acestea sunt în continuare consumate. Pe msdn dacă citim cu atenție pagina care descrie metoda Close() o sa gasim
Close does not always free the read and write handles to a queue, because they might be shared.
Deși pare ciudat la prima vedere metoda Close() eliberează resursele folosite de instanta. Nu oprește instanta sa nu mai consume și alte mesaje din queue.
Solutia pe care o propun este sa ne dezabonam de la evenimentul de ReceiveCompleted înainte sa apelam Close():
msmq.ReceiveCompleted -= m_ReceiveCompleted;
O alta solutie ati putea spune ce este ca în metoda ReceiveCompleted sa nu mai apelam BeginReceive() cînd anumite condiții sunt îndeplinite. Problema in cazul acesta ar fi ca noi deja am consuma un mesaj de pe queue, deși poate nu ar trebuii sa consuma mesajul respectiv.
Aceasta problema se poate manifesta și în cadrul unit test-elor, cînd mesajele din queue dispar pur și simplu și nu mai ajung la cine trebuie( cazul în care în mai multe unit teste consuma același queue, iar instantele la MessageQueue sunt statice).

Voi aveți alte soluții la aceasta problema?


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 …

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.

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…