{"action":"created","issue":{"url":"https://api.github.com/repos/celery/celery/issues/5109","repository_url":"https://api.github.com/repos/celery/celery","labels_url":"https://api.github.com/repos/celery/celery/issues/5109/labels{/name}","comments_url":"https://api.github.com/repos/celery/celery/issues/5109/comments","events_url":"https://api.github.com/repos/celery/celery/issues/5109/events","html_url":"https://github.com/celery/celery/issues/5109","id":369832205,"node_id":"MDU6SXNzdWUzNjk4MzIyMDU=","number":5109,"title":"be able to set connecting timeout for kombu from within celeryconfig / djangosettings","user":{"login":"sivang","id":310789,"node_id":"MDQ6VXNlcjMxMDc4OQ==","avatar_url":"https://avatars1.githubusercontent.com/u/310789?v=4","gravatar_id":"","url":"https://api.github.com/users/sivang","html_url":"https://github.com/sivang","followers_url":"https://api.github.com/users/sivang/followers","following_url":"https://api.github.com/users/sivang/following{/other_user}","gists_url":"https://api.github.com/users/sivang/gists{/gist_id}","starred_url":"https://api.github.com/users/sivang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sivang/subscriptions","organizations_url":"https://api.github.com/users/sivang/orgs","repos_url":"https://api.github.com/users/sivang/repos","events_url":"https://api.github.com/users/sivang/events{/privacy}","received_events_url":"https://api.github.com/users/sivang/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-10-13T19:15:04Z","updated_at":"2018-10-15T11:53:25Z","closed_at":null,"author_association":"NONE","body":"celery 3.1.25.\r\n\r\nI'm seeing a connecting linger when using celery to send messages through a rabbitmq server frontended with an AWS elb.\r\n\r\nConnection never close, and I'd like to make sure this is not something wrong with how kombu is connecting to RMQ to send messages, e.g. by not providing a defined timeout for the client connection which leaves the rabbitmq/ celery at the receiving end confused and never closing the connections even though it was for one message each. \r\n\r\nWhat would be the way to setup a timeout for kombu from Celery? I could not find anywhere in the docs.\r\n"},"comment":{"url":"https://api.github.com/repos/celery/celery/issues/comments/429822290","html_url":"https://github.com/celery/celery/issues/5109#issuecomment-429822290","issue_url":"https://api.github.com/repos/celery/celery/issues/5109","id":429822290,"node_id":"MDEyOklzc3VlQ29tbWVudDQyOTgyMjI5MA==","user":{"login":"sivang","id":310789,"node_id":"MDQ6VXNlcjMxMDc4OQ==","avatar_url":"https://avatars1.githubusercontent.com/u/310789?v=4","gravatar_id":"","url":"https://api.github.com/users/sivang","html_url":"https://github.com/sivang","followers_url":"https://api.github.com/users/sivang/followers","following_url":"https://api.github.com/users/sivang/following{/other_user}","gists_url":"https://api.github.com/users/sivang/gists{/gist_id}","starred_url":"https://api.github.com/users/sivang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sivang/subscriptions","organizations_url":"https://api.github.com/users/sivang/orgs","repos_url":"https://api.github.com/users/sivang/repos","events_url":"https://api.github.com/users/sivang/events{/privacy}","received_events_url":"https://api.github.com/users/sivang/received_events","type":"User","site_admin":false},"created_at":"2018-10-15T11:53:25Z","updated_at":"2018-10-15T11:53:25Z","author_association":"NONE","body":"But when about setting the timeout in the producer? is this it? -\nhttp://docs.celeryproject.org/en/latest/userguide/configuration.html#std:setting-broker_transport_options\n\nOn Sun, Oct 14, 2018 at 5:13 PM Josue Balandrano Coronel <\nnotifications@github.com> wrote:\n\n> I believe this configuration exists but you will have to update to 4.0\n>\n> http://docs.celeryproject.org/en/latest/userguide/configuration.html#broker-connection-timeout\n>\n> —\n> You are receiving this because you authored the thread.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/celery/celery/issues/5109#issuecomment-429629824>, or mute\n> the thread\n> <https://github.com/notifications/unsubscribe-auth/AAS-BYuJ9crUE1ONKiTlDkx2LLIANSizks5uk0aigaJpZM4Xax8e>\n> .\n>\n"}}
{"actor":{"display_login":"sivang"}}