Change Details

TBD

This diff introduces small changes to the AMQP client initialization function. The good point is to wait until the client is ready for the initialization call. In case the AMQP server is not available we shouldn't defer connection/reconnection waiting to the first call of the `send` or `ack` and stop the execution of the app right after the maximum reconnection failures is reached. The `init()` is called from the main and in tests in the [[ https://github.com/CommE2E/comm/blob/ceb853937917a3688ae21fb628256fa3e52ec947/services/tunnelbroker/test/AmqpManagerTest.cpp#L19 | SetUp section ]]. That's why is a good point to wait for a successful connection here.

TBDhis diff introduces small changes to the AMQP client initialization function. The good point is to wait until the client is ready for the initialization call. In case the AMQP server is not available we shouldn't defer connection/reconnection waiting to the first call of the `send` or `ack` and stop the execution of the app right after the maximum reconnection failures is reached. The `init()` is called from the main and in tests in the [[ https://github.com/CommE2E/comm/blob/ceb853937917a3688ae21fb628256fa3e52ec947/services/tunnelbroker/test/AmqpManagerTest.cpp#L19 | SetUp section ]]. That's why is a good point to wait for a successful connection here.