Issue with multiple concurrent reads about connect-mongostore HOT 3 OPEN

Was there ever a solution to this? I seem to have exactly the same setup and the same issue.

from connect-mongostore.

I don't think there was ever a solution for the module itself. In my case, I made a small middleware to make sure there is no concurrency in the session middleware for the first request.

The middleware is divided into two parts surrounding express.session() in the middleware chain. There are three stages of work: "no requests", "queue" and "normal operations". Both parts share the stage and queue variables.

The first part works as follows:

• When in "no requests", it will switch to the "queue" stage and call next().
• In the "queue" stage, the next functions passed to the this middleware is pushed into the queue but not executed.
• In "normal operations", next() is called

The second part works as follows:

• If there are queued functions, call each one emptying the queue
• Set stage to "normal operations"
• Call next()

from connect-mongostore.

Makes sense, thanks.

from connect-mongostore.