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
{{ message }}
This repository has been archived by the owner on Mar 14, 2019. It is now read-only.
For some reason when I update my server code and the meteor server restarts, the only way for me to get file uploads working again is to close my client window and re-open it. Is there some kind of JS thread on the client that is keeping the client from working when the server restarts?
The text was updated successfully, but these errors were encountered:
At the moment each collectionFS is handed its own connection to the server (not to block the normal ddp patch traffic) I've had similar issue with reconnecting meteor apps in general - I'm convinced that this will improve. I'm also planning a complete rewrite of the client side code.
Turning off thread behaviour
The queue on the client has some thread like behaviour - This can be overwritten by:
_queueCollectionFS.spawns=0;//0 = we dont spawn into "threads", 1..n = we spawn multiple "threads"
I dont think it would solve the issue, but for the sake of debugging
After server boot - if client is not reconnecting
In console you can try:
Meteor.reconnect();
This will reconnect the default Meteor connection - if this solves the issue then its a Meteor issue - Well, Bleeding edge :)
Some quick intro, I'll try to confirm issue in a week or two - would be nice to know if Meteor is clever enough to reconnect all client connections or if focus is only on default_connection.
For some reason when I update my server code and the meteor server restarts, the only way for me to get file uploads working again is to close my client window and re-open it. Is there some kind of JS thread on the client that is keeping the client from working when the server restarts?
The text was updated successfully, but these errors were encountered: