Results 1 to 3 of 3

Thread: onDisconnect not always called?

  1. #1
    Join Date
    Mar 2011

    Question onDisconnect not always called?

    I have a simple library that keeps track number of concurrent connections for each user to prevent abuse.
    For RTMP whenever play() is called, add one to the hashtable, and onDisconnect() is called, subtract one from the hashtable.

    It has been working great until recently. According to the log file, sometime the client just went away without onDisconnect being called. Concurrent count for the user will keep going up for each play request until it reaches the limit.

    Am I doing this right? Or do I have to use other method to detect client disconnect?


  2. #2
    Join Date
    Sep 2011


    OnDisconnect() will always be called when a client leave due to a disconnect or a timeout.

    Have you changed something recently in your Wowza configuration or code configuration?
    Was this code you put together definitely working before or is it possible you have just discovered that it didn't work from the beginning?


  3. #3



    The sourcecode for the connectioncounts HTTPProvider is here.

    Take a look at that for a working example. If you find that the unmodified connectioncounts HTTPProvider is not correctly reporting the counts, please mention this and someone will point you towards a tutorial for submitting a bug report.

Similar Threads

  1. Plugin event "onDisconnect" not called when HLS
    By Luga91 in forum General Forum
    Replies: 1
    Last Post: 11-04-2013, 11:00 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts