[gwt] Disconnect request stuck in 2.0.6 about atmosphere-javascript HOT 7 CLOSED

This issue only happens with GWT. I try reproducing using the atmosphere-chat and everything works fine.

from atmosphere-javascript.

The same issue happened for me on 2.1.0 and 2.0.7. Using enableProtocol and trackMessageSize flags.
I also using GWT

from atmosphere-javascript.

Looks like sync disconnection never get response from server until it kills the connection. I tried to add OnDisconnectInterceptor and it didn't help.

from atmosphere-javascript.

To reproduce issue easier you need to set up maxStreamingLength to 50K or 1MB instead of default and set up streaming transport. Unfortunatelly i didn't tried to reproduce the issue on examples.

Just tried to set disconnect request to async, however it brings another problem:
4 reconnections happens succesfully but messages from server becomes corrupted and I get exceptions:
"Uncaught Error: message length" in _trackMessageSize function

from atmosphere-javascript.

Here snap from YourKit Tomcat 7.0.42:

from atmosphere-javascript.

@gromozekas Please open another issue, this is not the same. Also, upgrade to Tomcat 7.0.47 and redo your tests as Tomcat .42 suffer many internal deadlock. If you are still able to reproduce, try to grab a thread dump with line number, will be easier for me to debug. Thanks!

from atmosphere-javascript.

Closed as fixed. Please re-open if you are still able to reproduce.

from atmosphere-javascript.