-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix/issue 509 #513
Fix/issue 509 #513
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
||
self._log.debug('Connection State %s channel state %s' | ||
% (mq_connection.is_open, | ||
mq_channel.is_open)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest to disable that message - it's on a hot code path. OTOH, it's DEBUG
level, and we should not encourage to run DEBUG
as default level either. Hmm, so probably ok... :-)
@@ -22,6 +22,8 @@ | |||
|
|||
from .wfprocessor import WFprocessor | |||
|
|||
pika.connection.Parameters.DEFAULT_HEARTBEAT_INTERVAL = 0 | |||
pika.connection.Parameters.DEFAULT_HEARTBEAT_TIMEOUT = 0 | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want that to be the default behavior for EnTK and RBMQ? Do we have issues only with one user and one machine or is the heartbeat_interval going to be a more general issue? If the former, then should we keep the default as it has been so far and enable setting the interval/timeout to a specific value via env variables?
Closing this PR as there is an easy workaround |
This is to take care of cases like issue #509. I still to find a proper fix for that one.