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)
{
Console.WriteLine(DateTime.Now.ToString());

MessageQueue msmq = (MessageQueue) sender;
msmq.BeginReceive();
}
Intr-un anumit moment, dorim sa oprim consumul de mesaje din queue. Pentru acest lucru apelam
msmq.Close()
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;
msmq.Close();
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?

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…