Page MenuHomeDevCentral

Recover when the connection is closed via RabbitMQ management plugin
ClosedPublic

Authored by dereckson on Jan 12 2017, 08:02.
Tags
None
Referenced Files
F2829025: D825.id2086.diff
Fri, Apr 19, 06:43
F2827460: D825.id2089.diff
Fri, Apr 19, 00:09
Unknown Object (File)
Thu, Apr 18, 08:14
Unknown Object (File)
Sun, Apr 14, 22:16
Unknown Object (File)
Sun, Apr 14, 22:04
Unknown Object (File)
Sat, Apr 13, 01:25
Unknown Object (File)
Wed, Apr 10, 10:21
Unknown Object (File)
Tue, Apr 9, 12:56
Subscribers
None

Details

Summary

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

Repository
rVIPER ViperServ scripts
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

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.