{"action":"opened","issue":{"url":"https://api.github.com/repos/dandemeyere/responsys-api/issues/24","labels_url":"https://api.github.com/repos/dandemeyere/responsys-api/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/dandemeyere/responsys-api/issues/24/comments","events_url":"https://api.github.com/repos/dandemeyere/responsys-api/issues/24/events","html_url":"https://github.com/dandemeyere/responsys-api/issues/24","id":55354373,"number":24,"title":"Wrap all calls to responsys with a `Timeout::timeout(X) {}`","user":{"login":"evantahler","id":303226,"avatar_url":"https://avatars.githubusercontent.com/u/303226?v=3","gravatar_id":"","url":"https://api.github.com/users/evantahler","html_url":"https://github.com/evantahler","followers_url":"https://api.github.com/users/evantahler/followers","following_url":"https://api.github.com/users/evantahler/following{/other_user}","gists_url":"https://api.github.com/users/evantahler/gists{/gist_id}","starred_url":"https://api.github.com/users/evantahler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/evantahler/subscriptions","organizations_url":"https://api.github.com/users/evantahler/orgs","repos_url":"https://api.github.com/users/evantahler/repos","events_url":"https://api.github.com/users/evantahler/events{/privacy}","received_events_url":"https://api.github.com/users/evantahler/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-24T01:48:51Z","updated_at":"2015-01-24T01:48:51Z","closed_at":null,"body":"I've noticed that responsys' API often becomes un-responsive when you have many simultaneous connections.  For example, maybe you have 40 resque workers trying to update responsys with a new column of data about your users...  The client doesn't see a 500, error, or timeout.  It just... hangs.  I've seen processes last over a day.  This can \"clog\" up your resque queues (or your unicorns) and cause bad things to happen.  \r\n\r\nIn all cases, I would prefer that an exception be **truly** thrown so it can be handled in the normal way (error to users, resque-retry, etc).\r\n\r\nI believe that this is actually an error with `savon`, but we have the opportunity to provide safety to users of the gem. "}}