sometimes connections fail to finish, leaving the browser displaying the 3-dot rotation thing.

[rustycar54]

sometimes connections fail to finish, leaving the browser displaying the 3-dot rotation thing.

[aliasaria]

I feel like this is an issue with Socket.IO -- it tries a number of different ways to connect to get a two-way channel built. Do you know what form of connection socket-io formed? (you can see it in your cookies sometimes)

[rustycar54]

Well, my cookies don't look very helpful. Firefox has 5 cookies, named __utm{a,b,c,z} and scrumscrum-cookie.

Only utmz looks even slightly promising, it says 18214395.1308764390.1.1.utmscr=(direct)|utmccn=(direct)|utmcmd=(none)'

I decided to try a wireshark capture to see if I could see anything that way.

That looks much more promising. I could probably find a place to stick the capture if that would help...

Here is the top-level dump of the last few packets (nothing happens for a while (multiple seconds) after the last packet here):

"520","56.308979","10.5.21.36","10.5.20.7","TCP","windlm > 8011 [ACK] Seq=1426 Ack=17787 Win=64842 Len=0"
"521","56.308987","10.5.21.36","10.5.20.7","TCP","hello > 8011 [ACK] Seq=1454 Ack=208840 Win=64820 Len=0"
"522","56.308994","10.5.21.36","10.5.20.7","TCP","nmsp > 8011 [ACK] Seq=2487 Ack=93789 Win=65080 Len=0"
"523","56.309001","10.5.21.36","10.5.20.7","TCP","psmond > 8011 [ACK] Seq=1899 Ack=30424 Win=64842 Len=0"
"524","56.510089","10.5.21.36","10.5.20.7","TCP","finle-lm > 8011 [ACK] Seq=3888 Ack=31655 Win=65536 Len=0"
"525","56.510225","10.5.21.36","10.5.20.7","TCP","ea1 > 8011 [ACK] Seq=5390 Ack=279483 Win=65536 Len=0"
"526","58.259411","10.5.21.36","10.5.20.7","TCP","finle-lm > 8011 [PSH, ACK] Seq=3888 Ack=31655 Win=65536 Len=581"
"527","58.260477","10.5.20.7","10.5.21.36","TCP","8011 > finle-lm [PSH, ACK] Seq=31655 Ack=4469 Win=16064 Len=186"
"528","58.421116","10.5.21.36","10.5.20.7","TCP","finle-lm > 8011 [ACK] Seq=4469 Ack=31841 Win=65350 Len=0"
"529","58.933010","10.5.21.36","10.5.20.7","TCP","finle-lm > 8011 [PSH, ACK] Seq=4469 Ack=31841 Win=65350 Len=464"
"530","58.937041","10.5.20.7","10.5.21.36","TCP","8011 > finle-lm [PSH, ACK] Seq=31841 Ack=4933 Win=17216 Len=241"
"531","59.125281","10.5.21.36","10.5.20.7","TCP","finle-lm > 8011 [ACK] Seq=4933 Ack=32082 Win=65108 Len=0"
"532","59.125302","10.5.20.7","10.5.21.36","TCP","8011 > finle-lm [PSH, ACK] Seq=32082 Ack=4933 Win=17216 Len=404"
"533","59.146440","10.5.21.36","10.5.20.7","TCP","finle-lm > 8011 [PSH, ACK] Seq=4933 Ack=32486 Win=64704 Len=416"
"534","59.168731","10.5.20.7","10.5.21.36","TCP","8011 > finle-lm [ACK] Seq=32486 Ack=5349 Win=18368 Len=2920"
"535","59.168775","10.5.20.7","10.5.21.36","TCP","8011 > finle-lm [PSH, ACK] Seq=35406 Ack=5349 Win=18368 Len=1283"
"536","59.169422","10.5.21.36","10.5.20.7","TCP","finle-lm > 8011 [ACK] Seq=5349 Ack=35406 Win=65536 Len=0"
"537","59.169537","10.5.21.36","10.5.20.7","TCP","finle-lm > 8011 [ACK] Seq=5349 Ack=36689 Win=64252 Len=0"

If you need me to do some kind of different capture, or dump packet contents, or whatever I'm up for that.

Thanks!

Rusty

[aliasaria]

You need to look at the cookie called socketio to see what type of connection socket io is using

[rustycar54]

When the connection is broken (including when the "leds are blinking"), there is no cookie (no surprise there).
On a machine which is having trouble staying connected, the cookie is 'jsonp-polling' (browser was firefox, I think).
On a machine which seems to be having no problems staying connected (has been for 5 or 6 days, although with 4 of those days being idle), the cookie is 'websocket' (browser was Google Chrome).

-----Original Message-----
From: aliasaria [mailto:[email protected]]
Sent: Thursday, June 23, 2011 6:44 AM
To: Carruth, Rusty
Subject: Re: [scrumblr] sometimes connections fail to finish, leaving the browser displaying the 3-dot rotation thing. (#22)

You need to look at the cookie called socketio to see what type of connection socket io is using

Reply to this email directly or view it on GitHub:
#22 (comment)

[rustycar54]

(sorry, I was sick Thursday through Sunday (yesterday), so could not reply sooner than today)