[Live-devel] Re : Max limit for RTSPClientSession instances?

[Renato MAURO (Libero)]

Re: [Live-devel] Max limit for RTSPClientSession instancesHi Alkassoum, hi Ross.

    Alkassoum, thank you very much, you solved my problem.

    Ross, thank you for your suggestion.


    Renato MAURO


  ----- Original Message ----- 
  From: ahmoud alkassoum 
  To: LIVE555 Streaming Media - development & use 
  Sent: Tuesday, July 22, 2008 3:08 AM
  Subject: [Norton AntiSpam] [Live-devel] Re : Max limit for RTSPClientSession instances?


  Hi Mauro,
  If you are running your application under windows you might have the same problem i had few months ago.
  My problem was due to an windows OS limitation on the number of sockets that can be open at any one time. 
  On windows the FD_SETSIZE parameter have a default value of 64, so with that default value,
  the server can only handle 64/2 = 32 clients at the same time ( 2 sockets
  per client). So to solve my problem i only had to increase the FD_SETSIZE
  parameter.

  Hope that this information did help you.

Alkassoum

  ----- Message d'origine ----
  De : Renato MAURO (Libero) <renatomauro at libero.it>
  À : LIVE555 Streaming Media - development & use <live-devel at ns.live555.com>
  Envoyé le : Lundi, 21 Juillet 2008, 16h05mn 15s
  Objet : Re: [Live-devel] Max limit for RTSPClientSession instances?


  >you may have run into a limit - in your operating system - of how many open files it can have;

  Thank you for your fast response. 

  I'm not reading data from files; my application receives data from a custom HW and uses Live555 to receive the streams from the HW and offer them through RSTPServer. I found that the 36 input streams are well received. The first 32 (and just now I reached 34) clients are well accepted. Using TcpView, I see 210 active sockets, ie. (36 in + 34 out)*(1 rtp + 2 UDP) = 210; besides there is one RTP socket opened and closed due to the 35th client's periodic attempt to get its stream.
  For your information, I have 37 environments, each with its own doEventLoop thread; one is for the unique RTSPServer instance and the others for the 36 RTSPClient instances. The RSTPServer has 36 session instances, which are fed via circular buffer (a new DeviceSource).

  Do you think I run into an "max open socket" limit (even if 210 is much less than 65535)?

  Thank you very much,

      Renato MAURO



    ----- Original Message ----- 
    From: Ross Finlayson 
    To: LIVE555 Streaming Media - development & use 
    Sent: Monday, July 21, 2008 1:56 PM
    Subject: Re: [Live-devel] Max limit for RTSPClientSession instances?


          I wrote an RTSPServer application using Live555. I have 36 different sessions, each with one video subsession. It works and have one limit only: it seems to be impossible to serve more than 32 client requests at a time(no difference between 32 clients on the same session or one client on 32 out of 36 sessions). On the client side, the , rtspClient->sendOptionsCmd(url) methos fails.

          I will debug my application more deeply in order to understand where, on the server side, the client request is not satisfied; by now my "high level analysis" question is: is there any max limit for RTSPClientSession instances?


    Not in our code; however, you may have run into a limit - in your operating system - of how many open files it can have (for each process) at a time.  Depending on your OS, there should be a way to increase that limit.
-- 
    Ross Finlayson
    Live Networks, Inc.
    http://www.live555.com/


----------------------------------------------------------------------------


    _______________________________________________
    live-devel mailing list
    live-devel at lists.live555.com
    http://lists.live555.com/mailman/listinfo/live-devel



------------------------------------------------------------------------------


  _______________________________________________
  live-devel mailing list
  live-devel at lists.live555.com
  http://lists.live555.com/mailman/listinfo/live-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20080722/565437ae/attachment.html>