Null Pointer Exception on MuxAdaptor.prepareMuxer

[mustafaboleken]

It occurred by one enterprise user.

It's reported by New Relic

Version: 2.8.0 EE

Stack Trace:

{ "errorDetail": "java.lang.NullPointerException: This pointer address is NULL.\n\tat org.bytedeco.ffmpeg.avformat.AVFormatContext.nb_streams(Native Method)\n\tat io.antmedia.muxer.MuxAdaptor.prepareMuxer(MuxAdaptor.java:1789)\n\tat io.antmedia.muxer.MuxAdaptor.startRtmpStreaming(MuxAdaptor.java:1910)\n\tat io.antmedia.muxer.MuxAdaptor.tryToRepublish(MuxAdaptor.java:1989)\n\tat io.antmedia.muxer.MuxAdaptor.lambda$endpointStatusHealthCheck$6(MuxAdaptor.java:1958)\n\tat io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:1040)\n\tat io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:1016)\n\tat io.vertx.core.impl.ContextImpl.emit(ContextImpl.java:335)\n\tat io.vertx.core.impl.ContextImpl.emit(ContextImpl.java:328)\n\tat io.vertx.core.impl.ContextInternal.emit(ContextInternal.java:206)\n\tat io.vertx.core.impl.VertxImpl$InternalTimerHandler.run(VertxImpl.java:1034)\n\tat io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)\n\tat io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:159)\n\tat io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)\n\tat io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)\n\tat io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)\n\tat io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)\n\tat io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)\n\tat io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)\n\tat io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.base/java.lang.Thread.run(Thread.java:840)\n", "instanceId": "21f7168c-e452-45fc-8b81-5fb86cee73a2", "instanceType": "Community", "instanceVersion": "2.8.0", "newrelic.source": "api.logs", "timestamp": 1706378401733 }

[burak-58]

It is hard to understand the problem without whole logs. I guess it occurs while a stream is closing. So it may not affect the active broadcast.