This repository was archived by the owner on Jan 15, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 15, 2021. It is now read-only.
Lost context reported using socket.io and/or sticky-session #114
Description
Issued forked from here: #108 (comment)
I am on the latest node and latest express versions and am getting this problem as well, but not only for onResponseEnd but also for onResponseSend.
But: I am using cluster to start multiple child processes. Because I am using socket.io and a client always needs to talk to the same worker, I am also using sticky-sessions (https://socket.io/docs/using-multiple-nodes/) -> https://github.com/indutny/sticky-session.
As this "hack" requires the master to listen to 80 and forwards the message to a worker on a random port ( -> app.listens(0, localhost) ) I am sure this is the cause for the issue
Metadata
Metadata
Assignees
Labels
No labels
Activity
nikmd23 commentedon Jun 11, 2017
Thanks for this report Jeremy A. Prescott (@japrescott)
We'd love to have a chat with you about how you're using Glimpse, what's useful and what isn't. It shouldn't take more than 30 mins and there's no need to prepare in advance. If you're interested, just pick a time slot over at https://calendly.com/nikmd23/30min
Thanks!