Actions
Bug #365
closed
DG
DG
Consumerd can't be killed if unable to connect to the error socket
Bug #365:
Consumerd can't be killed if unable to connect to the error socket
Start date:
10/10/2012
Due date:
% Done:
0%
Estimated time:
Description
When killing the session daemon, a consumerd, that was unable to connect to the error socket, does not quit.
DG Updated by David Goulet over 13 years ago
Related to bug 387 because the metadata thread does not quit if the consumer_thread_sessiond_poll thread dies.
It's related because there is a behavior issue.
DG Updated by David Goulet over 13 years ago
- Status changed from Confirmed to Resolved
This is fixed. Unable to reproduce the issue.
If the sessiond thread dies in the consumer daemon, everything goes down as well after every streams has hang up (if any existing). Considering that if the consumer error socket is bad for some reason, the sessiond thread will stop and notifies the other threads as well to gracefully quit.
Actions