OK, this is going to sound odd, and is a “head-scratcher” to us. We’ve been using WSE for quite some time now, and recently migrated to 4.8.17. We stream VOD via HLS w/ secure token enabled, and implement a custom module that supports secure token between our web servers FQDN and our WSE FQDN. This has been in production for years, leveraging a custom REST layer to make it all work. We have three different WSE implementations, on physically separate networks. We’ve recently realized that we are getting entries in the wowzastreamingengine_error.log stating HTTPStreamerAdapterCupertinoStreamer.onMediaFile[“path-to-video.ts”] :Session not accepted. For our implementations that have a lot of concurrency, the log is creating a lot of entries, but functionality is seemingly not impacted? Additionally, we create a custom detailed access file that all appears fine. AKA the request for the initial video is fine, but at some point in the stream, an error is logged, but the content seemingly recovers? Any help would be WONDERFUL!
Hi @Rich_Sokol hope you’re doing well!
I asked our Engine PM and he said:
“It’s weird that it fixes itself, it sounds like a memory leak we have in cupertino packetizer, but it’s behaving different. I would have them submit a support ticket to investigate if it’s a bug or if they’re potentially overloading the server. Depends on their workflow.”
Sorry I couldn’t be of more help to you.
