How did you solved ELB 60s disconnections for idle Websocket connections? I know... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

nivertech on Oct 8, 2013 | parent | context | favorite | on: Heroku WebSockets Now in Public Beta

How did you solved ELB 60s disconnections for idle Websocket connections? I know it can be increased, but not by too much.

EDIT: also when 2 years ago I did load testing with ELB and created 1 million concurrent WebSocket connections, I did received mail from Amazon asking what the hell I doing and was asked to stop it ;)

bgentry on Oct 8, 2013 [–]

The ELB idle connection rule still applies: https://devcenter.heroku.com/articles/heroku-labs-websockets...

You'll need to send some data every ~55s or so in order to keep the connection alive.

mh- on Oct 8, 2013 | [–]

This idle timeout can be increased by at least an order of magnitude now, upon request to AWS. Open a ticket.

Consider applying for YC's Fall 2026 batch! Applications are open till July 27.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact