You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The temporary queues used by re-core are living on "forever" (until re-core is disconnected) in some cases. I don't know what the behavior is that causes this but noted it while checking out the queues today.
The text was updated successfully, but these errors were encountered:
Initial thoughts: I think this usually happens when a worker doesn't
finish. The fsm is multithreaded so under present behavior if a worker
never finished, then that fsm thread will never run it's tare-down which
closes the channel. The temp queues are ephemeral, and will self destruct
after all clients disconnect.
On May 20, 2014 3:14 PM, "Steve Milner" [email protected] wrote:
The temporary queues used by re-core are living on "forever" (until
re-core is disconnected) in some cases. I don't know what the behavior is
that causes this but noted it while checking out the queues today.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8
.
The temporary queues used by re-core are living on "forever" (until re-core is disconnected) in some cases. I don't know what the behavior is that causes this but noted it while checking out the queues today.
The text was updated successfully, but these errors were encountered: