# Any downside in setting ApplicationTimeout to 0

**URL:** <https://community.wowza.com/t/any-downside-in-setting-applicationtimeout-to-0/96628>\
**Category:** Wowza Streaming Engine\
**Created:** [November 8, 2023, 4:00am UTC](https://community.wowza.com/t/any-downside-in-setting-applicationtimeout-to-0/96628 "2023-11-08T04:00:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yudong\_Li](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/yudong_li/32/814_2.png) [@Yudong\_Li](https://community.wowza.com/u/Yudong_Li)\
**Post date:** [November 8, 2023, 4:00am UTC](https://community.wowza.com/t/any-downside-in-setting-applicationtimeout-to-0/96628/1 "2023-11-08T04:00:37Z")

</div>

From the documentation:

> ### ApplicationTimeout
> 
> Length of time, in milliseconds, that the server will wait before shutting down an application to which no clients are connected. A **Timeout** value of **0** keeps applications running until the virtual host is shut down. If this value is not provided (or the section is commented out), the value set in the **VHost.xml** file is used.

My first question is if there is any downside in setting this timeout to be 0 and keep the application running even when there is no clients are connected?

Second question regarding this ApplicationTimeout is what to be considered as “clients are connected”. Does it refer to consumption, i.e. a player is consuming the m3u8/mpd feed? Does a running stream/RTMP push without consumption being still considered as “clients are connected”?