WebRTCRTPHandler.addNextTransportPacket: Hit max transport packets: 10000

Wowza Streaming Engine
1

I’m using webrtc to send live video between multiple users (multiple broadcasters, many more viewers) – after 5-10 minutes at 2000+ connections starting new broadcasts times out and this error starts showing up in the error log

WARN server comment 2020-12-28 10:18:16 - - - - - 57215.851 - - - - - - - - WebRTCRTPHandler.addNextTransportPacket: Hit max transport packets: 10000
WARN server comment 2020-12-28 10:18:17 - - - - - 57216.143 - - - - - - - - WebRTCRTPHandler.addNextTransportPacket: Hit max transport packets: 10000
WARN server comment 2020-12-28 10:18:17 - - - - - 57216.332 - - - - - - - - WebRTCRTPHandler.addNextTransportPacket: Hit max transport packets: 10000
WARN server comment 2020-12-28 10:18:17 - - - - - 57216.454 - - - - - - - - WebRTCRTPHandler.addNextTransportPacket: Hit max transport packets: 10000
WARN server comment 2020-12-28 10:18:17 - - - - - 57217.09 - - - - - - - - WebRTCRTPHandler.addNextTransportPacket: Hit max transport packets: 10000

What does the error mean?

Is it the reason new broadcasters time-out when trying to broadcast?

Wowza Streaming Engine Version

4.8.5.05 (build 20201006161917)

Wowza Streaming Engine Manager Version

4.8.5.05 (build 20201006161917)

(plan to update to 4.8.8 within a day)

2

I updated to the latest version the other day.

Wowza stops working after our users start using it for 5-20 minutes.

WebRTCRTPHandler.addNextTransportPacket: Hit max transport packets: 10000

is still what is written in the access and error logs.

Any clues on what needs to be changed to get this working?

3

Update: I also searched documentation for https://www.wowza.com/docs/search?phrase=addNextTransportPacket&s=rel

4

Hi - I posted this 10 days ago. It is still an issue. Any progress?

5

Morning Jason

I am seeing the same errors. We are using webrtc to deliver an audio only stream that broadcasts 24 hours a day 5 days a week. We typically have 300 to 500 concurrently connections and for us we see this error after approximately 3 to 4 hours of broadcasting a stream.

We are currently trying to mitigate the issue by restarting the server every three hours.

I was wondering if you ever found any sort of solution?

Thanks in advance.

Pip