Transport timeout too short cause Transport close..

[binlaniua]

my connect code

var socket;
if (that.isIE9()) {
	socket =  new SockJS(url)
} else {
	socket =  new SockJS(url, null, {transports:'websocket'})
}

i found code at "SockJS.prototype._connect"

var timeoutMs = (this._rto * Transport.roundTrips) || 5000;
this._transportTimeoutId = setTimeout(this._transportTimeout.bind(this), timeoutMs);

i log the timeoutMs is 698

in "websocket" my server reponse may be than this time... how to change it , did it has a setting ?

[antonselukh]

Let's see if this pull request solves the issue. I had similar client issues

[dazraf]

Hi, are the PR 412 and 413 sufficient to close this issue and release this feature in the next release please? thanks.

[chrislhardin]

1.3.0 doesn't have the transport timeout configuration feature. Is there a beta release or do I just need to build my own until it gets released? The current calculated timeout is way too short for my app.

[brycekahle]

@chrislhardin The referenced PR #413 has not been merged, thus it is not in master yet.