Skip to main content
Participant
Sep 23, 2008 1:23 AM UTC
Question

Netstream.Publish.Badname

If the internet connection drops for some reason I have the config set up to attempt to reconnect. Sometimes however, after a drop the connection will reestablish but with a "Netstream.Publish.Badname" error -- for all intents and purposes however the FMEncoder doesn't think there's anything wrong and continues to encode, but without publishing to the server. Usually it's fixed by either disconnecting and reconnecting again, or by stopping the encode, waiting til the network has been properly reestablished then running the encode job again.

Is there anyway I can avoid getting this error? Or, if not, is there any way I can get FME to recognise the error and restart or something? I have to have this streaming going 24/7 and if there's a network outage currently FME loses it and won't continue.
    This topic is closed to new replies. Start a new post to keep the conversation going.

    1 reply

    Inspiring
    Mar 16, 2014 9:03 PM UTC

    The same problem with latest FME 3.2 and FMS 4.5 default live app. Setting PublishTimeout=-1 serverside and/or increasing reconnect interval in FME does not help.

    Any workaround except custom live app with shared objects?

    Translate