Wowza Community

Please help troubleshooting unexpected error messages flooding the logs during WebRTC playback


I’ve notice a strange new error message when doing webrtc playback (from webrtc ingest) in WSE 4.8.18+1.

When playback starts I start getting these error messages in the log regularly, roughly every 2-3 seconds, up until the stream playback is finished.

ERROR server comment - RTPSessionDescriptionDataProviderBasic.getLoggingStreamName problem parsing streamName (null): java.lang.NullPointerException
        at java.base/$Parser.parse(
        at java.base/<init>(
        at com.wowza.wms.mediacaster.rtp.RTPSessionDescriptionDataProviderBasic.a(
        at com.wowza.wms.mediacaster.rtp.RTPSessionDescriptionDataProviderBasic.getSessionDescriptionData(
        at com.wowza.wms.mediacaster.rtp.RTPMediaCaster.getStreamInfo(
        at com.wowza.wms.mediacaster.rtp.RTPMediaCaster$
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.base/java.util.concurrent.ThreadPoolExecutor$
        at java.base/

It seemingly doesn’t cause any problems, streams work normally, but I’d still like to resolve this, to make logs usable again, and prevent any unexpected future problems.

Does anyone have idea what might cause this or how to proceed troubleshooting this?

Note: I’m using stream aliasing / resolving for stream playbacks.

I’ve also done tested it with some older WSE versions I had at hand, the error is present in 4.8.16+1, and 4.8.17+1, but works well in 4.8.14+9.

  • Sorry for the crazy title, new forum software didn’t let me post with a concise and useful title, as “it is not a complete sentence” :frowning:

Can you tell me what version of Java you are running and do you have it pointed to Engine properly?

Java support: Wowza Streaming Engine 4.8.18 is built on Java 11 (OpenJDK Java SE JRE 11.0.2), but can be used with Java versions 11 - 12. For more information, see Manually install and troubleshoot Java on Wowza Streaming Engine.

Also, please share the browser you are using. Are you using TCP or UDP?

Make sure you have all the req’s for 4.8.18 like the new Java requirement and also if you’re using Firefox, you need UDP as the ice candidate and you may need to have both TCP and UDP enabled.

There were a lot of breaking JAVA changes in 4.8.18 although I know you said you tested other versions as well.

Send in a support ticket if you still have issues so we can properly identify the cause of the log errors flooding.

I’ve been using OpenJDK 11.0.11, then upgraded to 11.0.15. I have both UDP and TCP enabled, publishing and playback is usually negotiating UDP.

I have tested with Chrome 100.0.4896.88 and Firefox 99.0, all combinations are producing the same issue.

I will open a support ticket shortly.

Ok please do because this rtp logging error was something we thought we’d fixed a few versions back so the engineers will want to investigate for sure.