Skip to main content
wanbli
Participating Frequently
October 6, 2006
Question

sometimes fms seems stop itself to respond to new connections.

  • October 6, 2006
  • 3 replies
  • 379 views
sometimes fms seems stop itself to respond to connect.
from clientside I do a connect and the server doesn't respond to client.
server side I see these processes:
4 S root 20552 1 0 85 0 - 16128 - Oct05 ? 00:02:11 ./fmsadmin -console -conf ./conf/Server.xml
4 S root 8410 1 0 85 0 - 9669 - Oct05 ? 00:00:11 ./fmsmaster -console
4 S root 8423 8410 0 85 0 - 24987 - Oct05 ? 00:00:12 /usr/local/fms/fmsedge -edgeports :1935 -coreports :19350 -conf /usr/local/fms/conf/Server.xml -adaptor _defaultRoot_ -name _defaultRoot__edge1
4 S liberotv 8426 8410 0 85 0 - 39002 schedu Oct05 ? 00:00:12 /usr/local/fms/fmscore -adaptor _defaultRoot_ -vhost _defaultVHost_ -app registry -inst -console -conf /usr/local/fms/conf/Server.xml -name _defaultRoot_:_defaultVHost_:registry:
4 S liberotv 17441 8410 0 82 0 - 36145 schedu 11:29 ? 00:00:00 /usr/local/fms/fmscore -adaptor _defaultRoot_ -vhost _defaultVHost_ -app rec -inst _*_966772 -console -conf /usr/local/fms/conf/Server.xml -name _defaultRoot_:_defaultVHost_:rec:_*_966772

and this connections on netstat:
netstat | grep 1935
tcp 0 0 localhost:37146 localhost:19350 ESTABLISHED
tcp 0 0 localhost:34111 localhost:19350 ESTABLISHED
tcp 0 0 localhost:19350 localhost:37146 ESTABLISHED
tcp 0 0 localhost:19350 localhost:34111 ESTABLISHED
tcp 12 0 <server_name>:1935 151.52.1.78:50279 ESTABLISHED

but the server is like "absent" from client perspective.

in the application.xml we have the configuration:
<LifeTime>
<RollOver>1200</RollOver>
<MaxCores>3</MaxCores>
</LifeTime>

and the server go out from this strange state when it's generated a new thread, after the 1200 seconds indicated in <RollOver> tag.

any help about this bug?

thanks in advantage for your time



    This topic is closed to new replies. Start a new post to keep the conversation going.

    3 replies

    Anonymous
    October 15, 2006
    1. what's the output of the onStatus event after you tried to connect
    2. does the client see a tcp connection to the server (netstat)
    3. isn't some firewall blocking outgoing port 1935 for the client
    4. what's the last line(s) in the FMS console
    wanbliAuthor
    Participating Frequently
    October 16, 2006
    thanks for your response.

    1. what's the output of the onStatus event after you tried to connect
    there is no output on the onStatus handler. the client do a connect and then have no response

    2. does the client see a tcp connection to the server (netstat)
    yes. the server is visible. we reach it by telnet.

    3. isn't some firewall blocking outgoing port 1935 for the client
    no there isn't

    4. what's the last line(s) in the FMS console
    console? in the fms2_admin.swf, there is no added line in the application log.

    the core is in a state like freezed. no one clients are responsed from the fmscore, until a new core start like configured in the application.xml:
    <LifeTime>
    <RollOver>1200</RollOver>
    <MaxCores>3</MaxCores>
    </LifeTime>

    and the fmscore thread freezed stay running with the new process forever. seem it doesn't follow the LifeTime tag configuration.

    this situation happens more or less every day, but it seems not linked to the machine where the server is running.

    any help?


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