We've lately been dealing with the occurrence of a strange "fatal errors detected by the Java Runtime Environment" in our Azure Kubernetes AntMedia server (v2.4.3) implementation. This results in a Kubernetes pod restarting, which disrupts the usability of our streaming app which uses AntMedia in the background (basically publishing/playing stops until new pod is initiated and running).
All the logs from AntMedia server are available here:
Question
Dalibor
Hi everyone,
We've lately been dealing with the occurrence of a strange "fatal errors detected by the Java Runtime Environment" in our Azure Kubernetes AntMedia server (v2.4.3) implementation. This results in a Kubernetes pod restarting, which disrupts the usability of our streaming app which uses AntMedia in the background (basically publishing/playing stops until new pod is initiated and running).
All the logs from AntMedia server are available here:
AntMedia-2.4.3-fatal-error-logs.txt
The fatal error occurs at: 8:56:11, 8:57:01, 9:01:31, 9:03:46.
Does anyone know why this happens? Is there any way of stopping this from happening?
Thanks in advance!
Link to comment
Share on other sites
Top Posters For This Question
4
4
1
1
Popular Days
Nov 7
3
Nov 15
1
Oct 14
1
Dec 20
1
Top Posters For This Question
Burak 4 posts
Dalibor 4 posts
Murat Eminoglu 1 post
Connessione 1 post
Popular Days
Nov 7 2022
3 posts
Nov 15 2022
1 post
Oct 14 2022
1 post
Dec 20 2022
1 post
Popular Posts
Dalibor
Hi all! Just to confirm that we've received the snapshot version of AntMedia server (v2.6.0-snapshot) with the fix for this issue, and it seems it has been solved (as we haven't reproduced it sin
Dalibor
Hi all! For anyone tracking this ticket, I can confirm that the issue has been isolated and reproduced by the AntMedia devs and it's being worked on at this moment. The fix should come as soon as
9 answers to this question
Recommended Posts