[peol]

Hi,

is anyone else seeing this lately?


Calls made between the first call and its response are lost (never getting any responses).

Not sure if this is by design or a bug, I'm seeing this on latest xbmc master git.

Cheers,
Andrée

[Mizaki]

I only use websocket for notifications personally and use normally HTTP POST for everything else. What does the xbmc debug log say?

Sometimes I get a problem where (I think) the four maximum requests are pending (normally images that'll 404) so all the others queue. Not noticed any missed notifications.

[peol]

I only use websocket for notifications personally and use normally HTTP POST for everything else. What does the xbmc debug log say?

Sometimes I get a problem where (I think) the four maximum requests are pending (normally images that'll 404) so all the others queue. Not noticed any missed notifications.

Weird, I did debug this last night and didn't found anything of interest. Now I see:

Code:

15:44:11 T:2928665696   DEBUG: JSONRPC Server: New connection detected
15:44:11 T:2928665696    INFO: JSONRPC Server: New connection added
15:44:11 T:2928665696   DEBUG: JSONRPC: Incoming request: {"method":"GUI.ShowNotification","params":{"title":"xbmc-frontend","message":"Attached to XBMC instance.","displaytime":6000},"id":"__id5","jsonrpc":"2.0"}
15:44:11 T:2928665696   DEBUG: JSONRPC: Calling gui.shownotification
15:44:11 T:3043196928   DEBUG: ------ Window Init (DialogKaiToast.xml) ------
15:44:11 T:2928665696   DEBUG: JSONRPC: Incoming request: {"method":"VideoLibrary.GetEpisodeDetails","params":{"episodeid":121,"properties":["showtitle"]},"id":"__id1","jsonrpc":"2.0"}
15:44:11 T:2928665696   DEBUG: JSONRPC: Calling videolibrary.getepisodedetails
15:44:11 T:2928665696    INFO: WebSocket: Frame with invalid length received
15:44:11 T:2928665696    INFO: WebSocket: Invalid frame received

The two other requests never show up in the debug output but I guess it's because of the invalid length stuff.

EDIT: I guess I should register this as a bug on trac, now it looks clear to me that something weird is going on.
EDIT 2: Reported on trac here: http://trac.xbmc.org/ticket/13848