Hello all,
I am running a Wowza server which publishes 24 hour pseudo-live streams, using the Media Cache to pull in files from cloud storage as needed.
While monitoring the streams & logs, I see several skipped videos due to Media Cache timeouts. The most common is “Read timed out”, but I see an occasional “Connection reset” as well.
MediaCacheHTTPByteReader.sendRequest[http://www.someurl.com]: java.net.SocketTimeoutException: Read timed out
MediaCacheHTTPByteReader.sendRequest[http://www.someurl.com]: java.net.SocketException: Connection reset
This happens frequently enough to cause drift from my original playlists over time due to videos being skipped.
Are there changes I can make to the Media Cache config to improve this? What are the potential trade offs?
Here is what I see as the relevant section of MediaCache.xml (NOTE: This is for a Wowza 3.6 server, plan to upgrade to 4 next month)
<!-- maximum number of concurrent connections this source will make back to the web server -->
<Property>
<Name>maxPoolSize</Name>
<Value>25</Value>
<Type>Integer</Type>
</Property>
<!-- HTTP request timeout -->
<Property>
<Name>httpReadTimeout</Name>
<Value>6000</Value>
<Type>Integer</Type>
</Property>
<!-- HTTP connection timeout -->
<Property>
<Name>httpConnectionTimeout</Name>
<Value>6000</Value>
<Type>Integer</Type>
</Property>
<!-- HTTP read request retry count -->
<Property>
<Name>httpReadRetries</Name>
<Value>3</Value>
<Type>Integer</Type>
</Property>
<!-- Close socket connection if Content-Length incorrect on byte range request -->
<Property>
<Name>closeConnectOnBadContentLength</Name>
<Value>false</Value>
<Type>Boolean</Type>
</Property>
<!-- HTTP send buffer size -->
<Property>
<Name>httpSendBufferSize</Name>
<Value>8000</Value>
<Type>Integer</Type>
</Property>
<!-- HTTP receive buffer size -->
<Property>
<Name>httpReceiveBufferSize</Name>
<Value>65000</Value>
<Type>Integer</Type>
</Property>
Thanks in advance