Skip to main content
K
Kut_Lee
Participant
August 8, 2011
Question

Error server log: Assert failed in .\TCMsgHandler.cpp line 70

  • August 8, 2011
  • 1 reply
  • 860 views

hi there,

im using FMS4 as origin server and connect to FVSS from CDN, whose FVSS version's FMS3.5. with this all, when it's played with flashplayer from CDN every each connect require just wrote sth in the server log file as below:

Mon 09:51:56 AM: Assert failed in .\TCMsgHandler.cpp line 70
Mon 09:51:56 AM: Assert failed in .\TCMsgHandler.cpp line 70
Mon 09:51:56 AM: Assert failed in .\TCMsgHandler.cpp line 70
Mon 09:51:56 AM: Connect : rtmp://live.mywebsite.com:1935/2011/monitor/

and due to these frequent errors the CDN Edge service would get shuted down. but after i changed the FMS4 into FMS3.5 with origin server everything just worked well.

Now my question is, is that a bug with FMS4 or? and what can be done so far if we want to go on use FMS4?

thanks for any kind great help.

thx.

    This topic has been closed for replies.

    1 reply

    Nikhil_Kalyan
    Nikhil_Kalyan
    Participating Frequently
    August 8, 2011

    Hi,

    Thanks for trying FMS.

    The scenario you mentioned does lead into this trouble. We are working on the fix for this , and I can update you once resolved. Thanks again for pointing us to the problem.

    K
    Kut_LeeAuthor
    Participant
    August 9, 2011

    thanks for your response.

    appreciate your great help.

    Nikhil_Kalyan
    Nikhil_Kalyan
    Participating Frequently
    August 11, 2011

    Update from dev on this issue:

    Looked at the assert, it's because the two versions connecting don't speak quite the same connect message and the newer one has three properties that the old won't send it.  However, there's no indication that it will do anything to the client because of the absence of these as they're only used for RTMFP and the asserts are hamless though annoying.

    I am unable to see any client disconnects or playback issues when the assert happens. Are you sure you got them consistently ? As long as there are no client disconnects, I think we are good with the current behavior (except for few extra lines in the logs )

    Thank you !

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