Set the try catch to not let the exception on receive crash hte mnt controller.
Updated the start command API. Now we can start a stopped queue with the command { "CMD" : 2005 , "QName" : "testQ2"}.
Task #83 serialisation & unmarshaling of the Autoscaling config request in BSON. Next step update the interface of the MngtController for creating configurations.
Added the BSON serialisation & tests for the auto scaling config requests.
Added the switch control for processing the add autoscaling configuration.
Started the db processing for creating auto scaling rule. Notice that the update auto scaling configuration FK for a queue is missing.
Added a secuirty check in the management controller in order to check wether we recieve a multi part ZMQ message.
finished the security check for multi part message.
Issue #83: Decoding all auto scaling request from the mng controller. In addition added the ability to get the last row id inserted using an SQL lite features. We made thread safe the access.
Almost finished the management controller BSON API for creating auto scaling configuration.
Issue #83 finished the API to store and assign an auto scaling rule to a logical queue at 3 different levels. Still need to be tested from the client API in unit tests.
Issue #83 Finished the test of the BSON interface to add autoscaling rule.
Now we can send a BSON request as
 { "CMD" : 2006 , "QName" : "testQ2" , "AUTOSCALING_NAME" : "confTest" , "AUTOSCALING_HOST" : { "AUTOSCALING_HOST_CPU" : 40 , "AUTOSCALING_HOST_RAM" : 30} , "AUTOSCALING_XCHANGE" : { "AUTOSCALING_XCHANGE_THR" : 20000}}
Issue #83 finishing the GET auto scaling rule API in BSon.
Now we can add an auto scaling rule with:
{ "CMD" : 2006 , "QName" : "testQ2" , "AUTOSCALING_NAME" : "confTest" , "AUTOSCALING_HOST" : { "AUTOSCALING_HOST_CPU" : 40 , "AUTOSCALING_HOST_RAM" : 30} , "AUTOSCALING_XCHANGE" : { "AUTOSCALING_XCHANGE_THR" : 20000} , "AUTOSCALING_Q" : { "AUTOSCALING_THR_PROD_EXCH" : 100000 , "AUTOSCALING_Q_PROD_EXCH" : 10000}}

But aslo simply get the auto scaling configuration by the 2007 cmd:
{ "CMD" : 2007 , "QName" : "testQ2"}

The answer is then a 2007 answer:
{ "CMD" : 2007 , "QName" : "testQ2" , "AUTOSCALING_NAME" : "confTest" , "AUTOSCALING_HOST" : { "AUTOSCALING_HOST_CPU" : 40 , "AUTOSCALING_HOST_RAM" : 30} , "AUTOSCALING_XCHANGE" : { "AUTOSCALING_XCHANGE_THR" : 20000} , "AUTOSCALING_Q" : { "AUTOSCALING_THR_PROD_EXCH" : 100000 , "AUTOSCALING_Q_PROD_EXCH" : 10000}}
finishing the auto scaling API in BSON is its unit test. GET and ADD methods have been developed.
Issue #89 corrected the bug.
1. Now the HCM is un-registrating at shutdown
2. The GCM cleans its host topology on shutdowh
3. The Queue table uses the IP address as FK
Closes Issue #89.
issue #88 the Global configuration manager sends also the hosts list. Before we were sending the queue host location from where the host were inferred, but this made the client impossible to see the host managers on which he can create queues. Now the issue is resolved. We have also implemented the update of configuration in case of delta in the host list.
Adding the RoQ installation script. Thanks to CDU !
Corrected bug: the timer cancel method was sometimes called when the timer were running, then a socket was used and makes a C++ Assert failed when it tried to close it. We add a synchronized method with lock (less overkill than a simple synchronize key word).
Close #90. Updated the return BSON object. Now the value is

{
	"RESULT" : 0 , "COMMENT" : "The auto scaling configuration for queue testQ2" ,
	"AUTOSCALING_NAME" : "confTest" ,
	"AUTOSCALING_HOST" : { "AUTOSCALING_HOST_CPU" : 40 , "AUTOSCALING_HOST_RAM" : 30} ,
	"AUTOSCALING_XCHANGE" : { "AUTOSCALING_XCHANGE_THR" : 20000} ,
	"AUTOSCALING_Q" : { "AUTOSCALING_THR_PROD_EXCH" : 100000 ,
	"AUTOSCALING_Q_PROD_EXCH" : 10000}
}