#1250
  • Created on
    2011-10-03 06:19
  • Reported by
    Havoc Pennington
  • Status
    Invalid
  • Priority
    Normal (3)
  • Assigned to
    -
  • Milestone
    2.0-M1
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

AMQP: Notifications on RPC peer lifecycle

If you have an RPC client, it often can't do anything while the RPC server is down (e.g. hasn't started yet). When starting both processes there can be a race.
Right now if the server is down you just get a bunch of stack traces.

It would be nice if the client could get messages when the server queue appears and disappears. Then, the client could cleanly wait for the server to be present.
Or if the server restarts, the client could put up a maintenance page (for example, if the client is a web app) during the time that it's down.
User picture
  on 2011-10-03 06:45 *
By Jonas Bonér
Milestone set to 2.0
Updating tickets (#1244, #1246, #1249, #1250, #1251, #1252, #1255)
User picture
  on 2011-10-07 06:41 *
By viktorklang
Summary changed from Notifications on RPC peer lifecycle to AMQP: Notifications on RPC peer lifecycle
User picture
  on 2011-11-22 08:45 *
By viktorklang
Status changed from New to Invalid
Updating tickets (#980, #1217, #1244, #1246, #1249, #1250, #1251, #1302)

AMQP should have a full overhaul.
User picture
  on 2011-12-14 16:49 *
By viktorklang
Milestone changed from 2.0 to 2.0-M1
Updating tickets (#1129, #1132, #1138, #1149, #1153, #1154, #1157, #1161, #1163, #1168, #1170, #1171, #1172, #1176, #1177, #1178, #1180, #1199, #1217, #1218, #1219, #1237, #1238, #1239, #1244, #1246, #1249, #1250, #1251, #1252, #1256, #1301, #1302, #1306, #1395, #1396, #1409, #1418, #455, #891, #895, #912, #956, #972, #1031, #1374, #880, #1125, #1146)