Results 1 to 2 of 2

Thread: Applications instance "hanging". How bad is that?

  1. #1
    Join Date
    Mar 2013

    Default Applications instance "hanging". How bad is that?


    I have a few applications defined on the Wowza server as in the image below:

    I have many stream files defined in [wowza-install-dir]/content folder. Some of the resources defined in the streams are down sometimes. So, when I start to receive a stream that defines a resource not currently available, then I stop that stream, there are some application instances that "hang" (as it is visible in the image). This happens either when I manually start/stop those streams from the web interface or when I start/stop them from an application built by me. I thought it is a bug in my applications but it is actually Wowza default behaviour.
    The number of such "hanging" application instances could grow big over time and I don't see any way to (manually) stop them, unless I restart Wowza (which is not nice).

    My questions are:

    1. How bad is to live them there? Do they eat up the server resources?

    2. Is there any way to stop them and "cleanup" everything?


  2. #2
    Join Date
    Dec 2007



    An application instance that has not expired yet but is not doing anything, is not draining significant resources. An app instance should go away in 60 seconds if there is no activity


Similar Threads

  1. with sdp ingest, video ok, no audio - "Bad packet length"
    By dteeter in forum Live Streaming and Encoder Discussion
    Replies: 2
    Last Post: 11-26-2013, 03:21 PM

Posting Permissions

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