# All Handler Threads In Use

**URL:** <https://community.wowza.com/t/all-handler-threads-in-use/44051>\
**Category:** Wowza Streaming Engine\
**Created:** [October 31, 2016, 4:47pm UTC](https://community.wowza.com/t/all-handler-threads-in-use/44051 "2016-10-31T16:47:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hayden\_myers](https://avatars.discourse-cdn.com/v4/letter/h/eada6e/32.png) [@hayden\_myers](https://community.wowza.com/u/hayden_myers)\
**Post date:** [October 31, 2016, 4:47pm UTC](https://community.wowza.com/t/all-handler-threads-in-use/44051/1 "2016-10-31T16:47:51Z")

</div>

I’ve discovered that all handler threads can be consumed if the number of startup streams matches or exceeds the number of handler threads, and all of the streams become unavailable. If we have a handler thread limit of 240 and 250 streams which should be running, but go unreachable, the handler threads are consumed constantly by mediacasters trying to reconnect. Our servers are already tuned to the recommended performance settings with regards to processor count, handler, and transport threads, as specified by the tuning documents. This also occurs in the latest version of Wowza Streaming Engine. Is there a way to make the mediacaster reconnects play nice?

---

<div class="post-metadata">

**Author:** ![Michelle\_B](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/michelle_b/32/394_2.png) [@Michelle\_B](https://community.wowza.com/u/Michelle_B)\
**Post date:** [December 23, 2016, 4:43pm UTC](https://community.wowza.com/t/all-handler-threads-in-use/44051/2 "2016-12-23T16:43:32Z")

</div>

Hi,

You can increase the handler threads allotted to MediaCasters (under the Virtual Host Processors of the [Performance Tuning](https://www.wowza.com/docs/how-to-do-performance-tuning) menu) so that it is higher than the number of streams. You can also have custom logic in place that removes the MediaCaster connections that are unhealthy.

Michelle