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
This wamp client uses the default anonymous auth, so its confusing how that could fail? Even more confusing is how it sometimes succeeds, and sometimes fails. I suspect this is due to proxy workers being a work in progress?
will_retry: false is pretty annoying, because i want my clients to always retry, regardless of the disconnection reason. I was under the impression that setting max_retries: -1 would force clients to always retry, but if will_retry is false then my client stays disconnected, which is highly undesirable. As a workaround I manually reconnect in the onclose callback if will_retry is false.
The text was updated successfully, but these errors were encountered:
guanzo
changed the title
proxy worker connection error results in will_retry: false
proxy worker intermittent connection error results in will_retry: false
Aug 16, 2020
connect(){returnnewPromise(resolve=>{constconn=this.connectionif(conn?.isConnected&&conn?.isOpen){resolve()return}constautobahnOpts={initial_retry_delay: 5,}constonOpen=async(session)=>{this.session=sessiontry{awaitthis._registerProcedures(session)}catch(e){debug(e)// TODO: Retry registrations?}debug('wamp session opened')resolve()}constonClose=(reason,details)=>{debug('wamp session closed',reason,details)resolve()// resolve even if error, autobahn will retry.// Force autobahn to always retry.if(!details.will_retry){debug('will_retry is false, manually reconnecting')clearTimeout(this.retryTimeoutId)this.retryTimeoutId=setTimeout(()=>this.connect(),5000)}}this.connection=baseConnectToRouter(onOpen,onClose,autobahnOpts)})}
Screenshot: https://i.gyazo.com/53bfb2180160e7d86cbee38f40683cef.png
This wamp client uses the default anonymous auth, so its confusing how that could fail? Even more confusing is how it sometimes succeeds, and sometimes fails. I suspect this is due to proxy workers being a work in progress?
will_retry: false is pretty annoying, because i want my clients to always retry, regardless of the disconnection reason. I was under the impression that setting
max_retries: -1
would force clients to always retry, but if will_retry is false then my client stays disconnected, which is highly undesirable. As a workaround I manually reconnect in the onclose callback if will_retry is false.The text was updated successfully, but these errors were encountered: