Connect timed out error, when and how to reproduce this error or did it reconnect automatically?
Closed this issue · 2 comments
uncaughtException: Connect timed out date=Wed Jan 16 2019 18:17:11 GMT+0000 (UTC), pid=187, uid=19270, gid=19270, cwd=/app, execPath=/app/.heroku/node/bin/node, version=v8.11.2, argv=[/app/.heroku/node/bin/node, /app], rss=316243968, heapTotal=223825920, heapUsed=167301368, external=5254698, loadavg=[0.84033203125, 0.82373046875, 1.134765625], uptime=16929355, trace=[column=36, file=/app/node_modules/apn/lib/connection.js, function=null, line=226, method=null, native=false, column=31, file=/app/node_modules/async-listener/glue.js, function=Timeout._onTimeout, line=188, method=_onTimeout, native=false, column=11, file=timers.js, function=ontimeout, line=498, method=null, native=false, column=5, file=timers.js, function=tryOnTimeout, line=323, method=null, native=false, column=5, file=timers.js, function=Timer.listOnTimeout, line=290, method=listOnTimeout, native=false], stack=[Error: Connect timed out,
at Connection. (/app/node_modules/apn/lib/connection.js:226:36),
at Timeout._onTimeout (/app/node_modules/async-listener/glue.js:188:31),
at ontimeout (timers.js:498:11),
at tryOnTimeout (timers.js:323:5),
at Timer.listOnTimeout (timers.js:290:5)]
Description/Steps to reproduce
Googling didn't turn up much, but some people say that high volumes of notifications can cause these crashes. Maybe some rate-limiting is required on these notification requests?
This has happened 3 times in OCC/HOI in the last 30 days.
But I don't how to reproduce.
Expected result
How to reproduce and handle it or avoid the time out arise?
Did it will automatically reconnect again?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.