You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we are using this module for a lot of users on our production server. After running the nodes for a while we are experiencing a lot of timeouts, even when increasing the timeout to 20 seconds.
We've been investigating this problem for some time but still have not found the culprit. We've had several hypotheses that we have not disproved to be the problem.
We thought the request.on('close') event could be called earlier than the 'end' event. This is not the case.
We thought that perhaps sockets were not closed properly, leaving a big pile of open connections. This is not the case.
Is anyone experiencing a similar problem?
The text was updated successfully, but these errors were encountered:
Which nodejs version are you using?
Have you monitored the memory usage of the nodejs app? Maybe we are running into a memory or something like that.
Does it break after a specific amount of requests?
Maybe we need some function which tells us the general stats (how many sessions, how many requests and so on) to query the nodejs server as soon as the heavy timeouts happen in your case.
Hi, we are using this module for a lot of users on our production server. After running the nodes for a while we are experiencing a lot of timeouts, even when increasing the timeout to 20 seconds.
We've been investigating this problem for some time but still have not found the culprit. We've had several hypotheses that we have not disproved to be the problem.
Is anyone experiencing a similar problem?
The text was updated successfully, but these errors were encountered: