Skip to main content
K
Kut_Lee
Participant
April 20, 2012
Question

errors when access reaches a large amount.

  • April 20, 2012
  • 1 reply
  • 609 views

hi there,

i'm using FMS4.5 to live rtmp, clients invokes FMS Server after connecting to it,

myNc.call("getInfo",new Responder(onCallInfoResult,onCallInfoFail));

and it works ok, even core.00.log is clean with errors.

but as i use it as origin server , core.00.log logged 4 errors each time when clients access it through FVSS edge server (FMS3.5) from my CDN provider :

2012-04-20 00:50:43 16374 (e)2581279 Assert failed in tincan/server/TCMsgHandler.cpp line 70 -

2012-04-20 00:50:43 16374 (e)2581279 Assert failed in tincan/server/TCMsgHandler.cpp line 70 -

2012-04-20 00:50:43 16374 (e)2581279 Assert failed in tincan/server/TCMsgHandler.cpp line 70 -

2012-04-20 00:50:43 16374 (e)2581279 Assert failed in tincan/server/TCMsgHandler.cpp line 70 -

what's worse, the server even gets overload and shuts down when access reaches a large amount of about 2000+ & 20+/s. 

2012-04-20 00:50:26 14052 (w)2581171 System memory load (92) is high. -

wondering if there's a solution for this situation?

    This topic has been closed for replies.

    1 reply

    S
    ShivenK
    Inspiring
    April 20, 2012

    Hi Lee,

    On a first look, it clearly seems as if there is a compatibility issue. Owing to the huge differences in the two FMS versions, this is bound to occur.

    Probably you can try setting up your own edge-origin config, both as FMS 4.5 and make sure there is nothing wrong with the configuration.

    Thanks!

    K
    Kut_LeeAuthor
    Participant
    April 20, 2012

    hi ShivenK, thanks for your reply. Sorry to say that for customer's production environment, it's not as simple as it is in test environment to change the both sides to a same vision of FMS.

    and for my understanding,  as a commercial software 4.5 should have the downward(backward) compatibility with 3.5.  actually i hope it dose. otherwise it's a pity to say this point would absolutely effect customers' consideration when discussing a purchase.

    and, back to the point, besides to synchronize the both sides, i'd like to discuss about some other way to fix this problem with the pratical condition i'm having with my customer.

    thank you all the same.

    thanks.

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