Page MenuHomeDevCentral

Recover when the connection is closed via RabbitMQ management plugin

Authored by dereckson on Jan 12 2017, 08:02.



Currently, Wearg stops sometimes to process messages.

In such case, the easiest method is to force the connection
to close on server-side. A disconnect on client side doesn't work.

To avoid to check the timer, call ::broker::on_tick again,
recheck the time, we simply ask the bot to reconnect.

Test Plan

Disconnect from the management plugin.
Check it's connected again.

Wearg partyline
07:59:31 <Wearg> [DEBUG] Can't get message from queue: a server connection error 320 occurred, message: CONNECTION_FORCED - Closed via management plugin /
                 Trying to reconnect...
07:59:42 <Dereckson> .tcl mq connected
07:59:42 <Wearg> Tcl: 1

Diff Detail

rVIPER ViperServ scripts
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

dereckson created this revision.Jan 12 2017, 08:02
dereckson accepted this revision.Jan 12 2017, 08:05
dereckson edited the summary of this revision. (Show Details)
dereckson edited the test plan for this revision. (Show Details)
This revision is now accepted and ready to land.Jan 12 2017, 08:06
This revision was automatically updated to reflect the committed changes.