[Live-devel] Problems with RTSP over TCP

[Thiago A. Corrêa]

Sorry for the delay, I'm only working 2 days/week on this project now....

>
>>   Whenever I set my client to connect to my server using TCP ( 
>> rtsp->setupMediaSubsession( *sub, False, d->useTCP ); ), if the client is 
>> killed or closed on the X button from Windows, the server starts using 
>> all avaliable CPU and becames mostly unresponsive....
>
> Can you reproduce this with the supplied RTSP server 
> ("testOnDemandRTSPServer") and RTSP client ("openRTSP -t") applications? 
> I wasn't able to.

Yes, I was able to reproduce with current ( 07.12.2004 ) version.
Just compiled the two, and used 
rtsp://192.168.0.2:7070/mpeg1or2AudioVideoTest on openRTSP -t
Then I used the Task Manager to kill openRTSP process and testOnDemandRTSP 
process is now consuming 98-99% of the CPU at all times.

>>    I'm guessing it could be related to the abbrupt disconnection ( recv() 
>> would return 0 ). Where does LIVE handle abbrupt disconnection of TCP 
>> sockets? Can't seam to find it :(
>
> The code that handles reading of RTP (or RTCP) data over TCP is 
> "RTPInterface::handleRead()" (in "liveMedia/RTPInterface.cpp").
>

Thanks, I'm trying to figure out how should I disconnect someone now :)
There is something strange that I found already: RTPOverTCP_OK is set but 
never tested.
Whatever value it holds is never used thru all of the Live code ( did a 
quick grep for it. )

Thanks in advance,
    Thiago A. Corrêa