Bug 11249 – SC rejects initial slimproto connections

Bug 11249 - SC rejects initial slimproto connections

Summary:

SC rejects initial slimproto connections

Status:	RESOLVED FIXED

Product:	SB Touch
Classification:	Unclassified
Component:	Networking
Version:	unspecified
Platform:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	MP
Assigned To:	Richard Titmuss

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-03-04 03:54 UTC by Richard Titmuss
Modified:	2009-09-08 09:13 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
wireshark trace showing error (350.92 KB, application/octet-stream) 2009-03-30 14:10 UTC, Richard Titmuss	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Richard Titmuss 2009-03-04 03:54:56 UTC

I've noticed that it takes a while for the slimproto part of SqueezePlay to connect, this happens on both the desktop and fab4. During the initial connection in the SC logs I see lots of :

    Slim::Networking::Slimproto::client_readable (405) client_readable: Client not found for slimproto msg op: STAT

On the SqueezePlay side I see, the following repeated a few times before a successful connection is made:

114209:659 INFO (SlimProto.lua:460) - connect to 192.168.1.1
114209:660 DEBUG (SlimProto.lua:552) - send opcode=HELO
114210:933 DEBUG (SlimProto.lua:396) - read opcode=strm #28
114210:934 DEBUG (SlimProto.lua:396) - read opcode=strm #28
114210:934 DEBUG (SlimProto.lua:396) - read opcode=setd #5
114210:934 DEBUG (SlimProto.lua:552) - send opcode=STAT
114210:935 DEBUG (SlimProto.lua:396) - read opcode=setd #5
114210:936 DEBUG (SlimProto.lua:552) - send opcode=STAT
114210:937 DEBUG (SlimProto.lua:396) - read opcode=aude #6
114210:937 DEBUG (SlimProto.lua:552) - send opcode=STAT
114210:937 DEBUG (SlimProto.lua:396) - read opcode=audg #22
114210:937 DEBUG (SlimProto.lua:552) - send opcode=STAT
114210:937 INFO (SlimProto.lua:604) - connection error: closed, reconnecting in 4.74 seconds
114210:937 INFO (SlimProto.lua:491) - disconnect

I believe (but have not confirmed with wireshark) that SC is closing connection.  It's not clear why it is rejecting the STAT packets. Actually it looks like I'm getting these messages periodically, every few seconds as well as on the initial connection.

Comment 1 Alan Young 2009-03-10 01:23:48 UTC

Richard, it would be great if you can reproduce this and get a wireshark capture. I have seen it once but have been unable to reproduce it. Alan.

Comment 2 Blackketter Dean 2009-03-25 12:21:57 UTC

Alan/Richard: does this need to be fixed for MP?

Comment 3 Richard Titmuss 2009-03-30 14:10:57 UTC

Created attachment 5001 [details]
wireshark trace showing error

See packets 1169 - 1207 in the trace for an example of the failure.

Comment 4 Alan Young 2009-04-03 06:13:46 UTC

SP is creating multiple simultaneous connection to SC, including two HELOs in a single packet.

Comment 5 Richard Titmuss 2009-04-03 08:56:22 UTC

i want to look at this for MP

Comment 6 Richard Titmuss 2009-04-06 05:53:10 UTC

Fixed in r5190.