Skip to main content
M
mbalestrini
Participant
March 23, 2007
Question

NetStream.Publish.Badname?

  • March 23, 2007
  • 3 replies
  • 819 views
Is there any other reason this error could happen, besides a stream with the same name already beeing published?

After having the application running for a period of time, in which many users publish and subscribe streams, my FMS stops letting the clients publish any more streams (returning always NetStream.Publish.Badname), and reseting the vHost is the only solution I found (I think that after a long period of time the problem also disappears, but I'm not completely sure).
I've made a test application where I can publish using any name I want, to be sure that I wasn't repeating names.

Thanks!
Maximo

    This topic has been closed for replies.

    3 replies

    A
    Anonymous
    February 4, 2009
    Ivan, can you give me the steps you're following and tell me exactly what you're seeing?
    Thanks,
    Jody
    I
    Ivan006
    Participant
    February 4, 2009
    Same issues here. Is there a time out setting that could make the encoder slower to connect and allow the server to settle?
    M
    mbalestriniAuthor
    Participant
    March 27, 2007
    The technical support guys (from the FMS Hosting) told me that this error is occurring because there is a saturation in the amount of streams that server is configured to handle. That's why once the limit is reached, no client can publish any more streams and they get the BadName error.
    Now they've increased that limit and the app has been working fine.
    M
    MilkDud58
    Participant
    March 20, 2008
    Does anyone know how to make this change? I am having the exact same issue currently.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices