Question
FMS2 Total Clients reach and FMS stop works
Hi everybody,
I have developed one application using FMS2 and Flash CS3 that creates a multi-publishing live stream. I am using FMS2 2.0.5 r88 with license template 2500-25.pro.
The application have two parts:
Publisher (can be max 900 distinct users);
Viewer (can be max 100 users);
After some “Publisher” client put its camera online the application put it in idle mode waiting for some “Viewer” client connect and ask to watch that stream. In this moment the Publisher client start to publish the video “LIVE” to the Viewer client and everything work good. When the Viewer client disconnect then the Publisher client goes to idle again and stop to sending the live stream into the FMS, waiting for another Viewer client again.
So far so good the application works great until now.
The main problem is that one bug appear all days after 15 hours connected (around 15:00 to 16:00 hours) the app stops to send any video to the Viewer client that only can see the blank video on the screen.
When this happened I saw the following info in the FMS2 Admin Panel:
FMS CPU is over 50% and its frequency almost linear in the graphic, rather the start scenario where the frequency was like a square-wave well formed and all streams was working good with good image.
Total Clients count 2500 or more
Active Clients count more than 750 – 1000 clients connected (max license used is 2500)
Rejected Clients around 10.
If I restart the application in the bug time the streams start to work again, the FMS CPU goes to square-wave in the graphic again jumping between 0 to 50% max, but some streams are swapped in the server memory cause is possible call for a stream and get another live, like a copy. The solution is to restart the FMS2 Server service and the FMS2 Admin services on the Windows Services Panel and everything go back into normal condition.
I hope somebody can help me, because I don’t know if the Total Clients is the problem or what I can do to avoid that processing problem. In fact is so curious why the FMS CPU grow in the time also.
Thank you everybody.
Willismar.
I have developed one application using FMS2 and Flash CS3 that creates a multi-publishing live stream. I am using FMS2 2.0.5 r88 with license template 2500-25.pro.
The application have two parts:
Publisher (can be max 900 distinct users);
Viewer (can be max 100 users);
After some “Publisher” client put its camera online the application put it in idle mode waiting for some “Viewer” client connect and ask to watch that stream. In this moment the Publisher client start to publish the video “LIVE” to the Viewer client and everything work good. When the Viewer client disconnect then the Publisher client goes to idle again and stop to sending the live stream into the FMS, waiting for another Viewer client again.
So far so good the application works great until now.
The main problem is that one bug appear all days after 15 hours connected (around 15:00 to 16:00 hours) the app stops to send any video to the Viewer client that only can see the blank video on the screen.
When this happened I saw the following info in the FMS2 Admin Panel:
FMS CPU is over 50% and its frequency almost linear in the graphic, rather the start scenario where the frequency was like a square-wave well formed and all streams was working good with good image.
Total Clients count 2500 or more
Active Clients count more than 750 – 1000 clients connected (max license used is 2500)
Rejected Clients around 10.
If I restart the application in the bug time the streams start to work again, the FMS CPU goes to square-wave in the graphic again jumping between 0 to 50% max, but some streams are swapped in the server memory cause is possible call for a stream and get another live, like a copy. The solution is to restart the FMS2 Server service and the FMS2 Admin services on the Windows Services Panel and everything go back into normal condition.
I hope somebody can help me, because I don’t know if the Total Clients is the problem or what I can do to avoid that processing problem. In fact is so curious why the FMS CPU grow in the time also.
Thank you everybody.
Willismar.
