{"action":"opened","issue":{"url":"https://api.github.com/repos/pika/pika/issues/1046","repository_url":"https://api.github.com/repos/pika/pika","labels_url":"https://api.github.com/repos/pika/pika/issues/1046/labels{/name}","comments_url":"https://api.github.com/repos/pika/pika/issues/1046/comments","events_url":"https://api.github.com/repos/pika/pika/issues/1046/events","html_url":"https://github.com/pika/pika/issues/1046","id":323148887,"number":1046,"title":"Inconsistent Blocking Connection hanging when consumer is idle","user":{"login":"sw360cab","id":777866,"avatar_url":"https://avatars0.githubusercontent.com/u/777866?v=4","gravatar_id":"","url":"https://api.github.com/users/sw360cab","html_url":"https://github.com/sw360cab","followers_url":"https://api.github.com/users/sw360cab/followers","following_url":"https://api.github.com/users/sw360cab/following{/other_user}","gists_url":"https://api.github.com/users/sw360cab/gists{/gist_id}","starred_url":"https://api.github.com/users/sw360cab/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sw360cab/subscriptions","organizations_url":"https://api.github.com/users/sw360cab/orgs","repos_url":"https://api.github.com/users/sw360cab/repos","events_url":"https://api.github.com/users/sw360cab/events{/privacy}","received_events_url":"https://api.github.com/users/sw360cab/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-15T10:01:31Z","updated_at":"2018-05-15T10:01:31Z","closed_at":null,"author_association":"NONE","body":"Pika: 0.12.0b2\r\nOS: Ubuntu\r\n\r\nWhen the connection is left idle for a long time (e.g. 10 hours). A consumer hangs and does not consume anymore messages. \r\nThis used to happen on pika 0.10 and it appeared to be solved in v. 0.11\r\nFollowing example in [Pika Examples](https://github.com/pika/pika/blob/master/examples/blocking_consume_recover_multiple_hosts.py), the issue could be reproduced.\r\n\r\nMoreover:\r\n- the same problem is difficult to reproduce when pushing to localhost (respect to RabbitMQ in another host/network)\r\n- no specific output from pika (at debug level)\r\n- RabbitMQ does not simply to complain about heartebeats\r\n- When pushing new messages, it appears a \"strange log\", that looks like it comes from pika application (that should consume)\r\n```\r\nrabbit                   | =WARNING REPORT==== 15-May-2018::08:59:41 ===\r\nrabbit                   | closing AMQP connection <0.1090.0> (192.168.1.1:44386 -> 172.18.0.2:5672):\r\nrabbit                   | client unexpectedly closed TCP connection\r\n```\r\n\r\nApart from big headaches, I would like to point out that in pika 0.11.2 this problem should not be present, but another takes places. When operating very long tasks connection is dropped as well.\r\n"}}
{"actor":{"display_login":"sw360cab"}}