Meteor + Heroku, Constant SockJS "Idle connection" Errors

#1

I’m on METEOR@1.4.3.1, but I’ve been getting this error since 1.3

I’m hosting using Meteor Buildpack Horse and am getting pretty constant errors from Heroku’s router. Note that these errors aren’t coming through the app at all. The errors along with Heroku’s support are included below.

I’ve found https://github.com/trinisofttechnologies/keepalive which looks like it may help, to be totally honest I’m pretty lost as where to look to solve this one.

Feb 27 12:00:28 atya heroku/router:  at=info method=GET path="/sockjs/info?cb=jwsh3pmw39" host=getatya.com request_id=e60ae8b9-2ee1-4486-9eb4-04b45b0b6053 fwd="67.6.191.206" dyno=web.1 connect=1ms service=4ms status=200 bytes=363 
Feb 27 12:02:23 atya heroku/router:  at=error code=H15 desc="Idle connection" method=GET path="/sockjs/901/y8fz6rvp/websocket" host=getatya.com request_id=eb040887-ac3d-45fe-8784-aedc8872a8c8 fwd="67.6.191.206" dyno=web.1 connect=0ms service=115021ms status=503 bytes= 

Feb 27 14:01:21 atya heroku/router:  at=info method=GET path="/sockjs/info?cb=l5ngxle6wm" host=getatya.com request_id=f547dd13-8227-4d6a-8812-7a4cbdb2495d fwd="67.6.191.206" dyno=web.1 connect=0ms service=3ms status=200 bytes=363 
Feb 27 14:03:52 atya heroku/router:  at=error code=H15 desc="Idle connection" method=GET path="/sockjs/776/kf4ucvgc/websocket" host=getatya.com request_id=051721c3-40b0-4aac-a8e3-a45fe8229aab fwd="67.6.191.206" dyno=web.1 connect=1ms service=150104ms status=503 bytes= 

Feb 27 16:02:34 atya heroku/router:  at=info method=GET path="/sockjs/info?cb=9tlees58sn" host=getatya.com request_id=c378ec45-bd4d-4af4-8bdc-570d5f53795e fwd="67.6.191.206" dyno=web.1 connect=0ms service=3ms status=200 bytes=363 
Feb 27 16:04:50 atya heroku/router:  at=error code=H15 desc="Idle connection" method=GET path="/sockjs/327/b3bzepg7/websocket" host=getatya.com request_id=b7ee328d-046d-433a-b092-3be1ba609dbb fwd="67.6.191.206" dyno=web.1 connect=1ms service=135108ms status=503 bytes= 

Feb 27 18:03:05 atya heroku/router:  at=info method=GET path="/sockjs/info?cb=oo6au27ylv" host=getatya.com request_id=8d146fb5-18ec-45ce-968c-e9d264229e9d fwd="67.6.191.206" dyno=web.1 connect=1ms service=4ms status=200 bytes=363 
Feb 27 18:05:46 atya heroku/router:  at=error code=H15 desc="Idle connection" method=GET path="/sockjs/628/o1gsgi3_/websocket" host=getatya.com request_id=f3e347a9-55e2-412b-bcd0-79f0ede200fb fwd="67.6.191.206" dyno=web.1 connect=0ms service=160025ms status=503 bytes= 

“The user begins the Websocket connection, and then just about 2 minutes later, the connection closes. Does the server send keepalives? Does the page creating the client connection send keepalives every 30 seconds or so? H15s most often happens because a header response is sent without a body, or something transforms/limits the body content so that it doesn’t match up with the header Content-Length.”

2 Likes
#2

DId you find any workaround?

#3

Seeing the same thing in our app, what’s the answer?

#4

I’ve been trying to find a solution for this, any news?

#5

Anybody? I’m having the same issue. thanks