Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

disconnecting called after disconnected status instantly. Log inside #70

Open
extempl opened this issue Dec 2, 2011 · 4 comments
Open

Comments

@extempl
Copy link

extempl commented Dec 2, 2011

Log:
Log screenshot

@extempl
Copy link
Author

extempl commented Dec 2, 2011

With reason set - situation the same.
And undefined on 9th row too.

After last row nothing happens more.

@extempl
Copy link
Author

extempl commented Dec 2, 2011

On another server I had another situation, without double disconnecting calls:
Log

@extempl
Copy link
Author

extempl commented Dec 2, 2011

This is what i have catched, while testing:
First disconnect:
log
Second:
log

@extempl
Copy link
Author

extempl commented Dec 2, 2011

So, I'm moved the next rows:

in _doDisconnect function:

this.connected = false; -> before this._changeConnectStatus(Strophe.Status.DISCONNECTED, null);

in disconnect function:

if(this.connected) { -> to the start of function

And it work fine for me.

Gordin added a commit to Gordin/strophejs that referenced this issue Jul 5, 2014
fixed _onDisconnectTimeout never trigger because maxRetries is undefined...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant