Skip to main content
R
rexdtripod
Known Participant
August 19, 2010
Question

NetConnection.Connect.IdleTimeOut every 10 minutes?

  • August 19, 2010
  • 1 reply
  • 1965 views

Am publishing a live stream from server to server per:

http://help.adobe.com/en_US/FlashMediaServer/3.5_Deving/WS5b3ccc516d4fbf351e63e3d11a0773d56e-7ffb.html

Here's the path my data is taking:

Encoder =======>FMS1(my server) republish ========>CDN========>viewing client

I noticed that about every 10 minutes or so the stream would seem to go down.

Looking at the logs at my FMS, I see that the application instance there is unloaded every 10 minutes like clockwork.  Message reads "Instance _definst_ is shutdown by the script...  Unloaded application instance _definst_."  This is preceeded by the "NetConnection.Connect.IdleTimeOut" message.

During the 10 minutes inbetween, the stream displays fine on the viewer.

The live docs say this message means "the publisher of the stream is idle and not transmitting data."  But the encoder is still encoding and transmitting data when this occurs.  What's causing this IdleTimeOut message?

    This topic has been closed for replies.

    1 reply

    A
    Anonymous
    August 20, 2010

    Hi,

    I haven't got your answer yet, but there are somethings that I will like to know to help me reach to the conclusion. Firstly, when you say that you recieve NetConnection.Connect.IdleTimeout, which clent are you talking about, i.e., is it the publisher, the republish application on your server, or the subscriber.

    When you say you see this message on application.00.log it seems that you are tracing the status of server 1(your FMS) to server2(CDN FMS) connection. Am I right?

    In that case can you share your app on server 1 used for republishing the livestream because I want to see the reason which is causing your app to shutdown. Also are you sure your encoder is still publishing and has not got disconnected or for some reason encoding is not happening.

    Also let me know which FMS are you on and which Encoder are you using.

    Thanks,

    Abhishek

    R
    rexdtripodAuthor
    Known Participant
    August 20, 2010

    Yes, tracing the status of server 1(my FMS) to server2(CDN FMS) connection.  You are correct.

    Unfortunately the republish code was provided to me by the CDN and is proprietary.  I'm not able to share it.

    But the problem appears to be related to how I'm archiving the stream at the first stop (my server).  I'm archiving h.264(f4v).  When I change the format of the stream name from mp4:streamname.f4v to simply streamname the issue seems to clear up.  I do see a note from the CDN to me stating "we do not have the ability to carry any arbitrary streamName. We need to set up the valid streamNames before hand."

    Looks like I'll have to pump an f4v formatted stream name to my server so that it can be archived in the right format and then somehow change the name when I republish it to them?  Not sure.  I think I'll have to work with them on it.

    Much obliged.

    A
    Anonymous
    August 20, 2010

    Hi,

    Which FMS are you on and also do you have any idea as to which FMS is your CDN using. Is mp4:streamname.f4v the name of the stream that your encoder is encoing stream at or the name with which you are republishing ? In either case I don't see the reason of timeout unless the stream itself is not getting published. Also, just out of my interest, please let me know in case you reach the reason for this timeout from your CDN.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices