Answer by Nithin Thomas · Jul 31, 2015 at 10:13 AM
Do you also see any "timecode jumped" errors in relation to stats database in your logs? Removing wms-stats.jar file may have interrupted the monitoring collection module, and prompted the service into a loop (hence the high CPU usage). You may have to archive and delete the files from /stats folder, restart Wowza services, and check you logs for errors again.
Answer by Michelle Brinker · Aug 07, 2015 at 08:39 AM
Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.
Answers Answers and Comments
2 People are following this question.
Inbound RTSP over SSL 2 Answers
Wowza steaming engine real-time monitoring issue 2 Answers
A simple Wowza authentication and authorization solution 1 Answer
Streaming Target Error 1 Answer
Trial version wowza restrictions 1 Answer
© 2005–2017 Wowza Media Systems, LLC. All rights reserved. Terms | Privacy | Trademarks | Legal