Skip to main content
S
savvior1
Participant
December 10, 2010
Question

FMS locks up randomly. Any ideas how to monitor this and have it restart automatically

  • December 10, 2010
  • 1 reply
  • 535 views

The subject says it all.

My client logs in to use our applicaiton and the server is not responsive.

THe service is up, however it does not respond to any requests.

I would like to scan for this proactively and reset FMS as neccessary

We are running Red hat linux if that helps

-NIck

    This topic has been closed for replies.

    1 reply

    S
    Shiraz Anwar
    Participating Frequently
    December 14, 2010

    I can conclude following points from your post, and please feel free to correct me if my assumptions are not correct:

    1. This lockup issue is intermittent.

    2. Sometimes user is able to login to your application and sometimes not.

    3. By lock-up you mean, FMS starts rejecting the connection and you can see from your admin console that the no. of rejected connection is increasing.

    4. After restarting your server, this lockup issue vanishes and same user is now able to login to your application without any hiccups.

    5. You are looking for an automatic detection for this lock-up issue that can also restart fms whenever this happens, right??

    I will like to suggest following that may help you to get out of this problem, please give it a try and let me know if any of these work for you:

    1. Check the cpu, network and memory usage whenever lock up happens.

    2. Check the number of connected users and connectionrate at this point.

    3. What FMS version you are using?

    4. There is a tag in "vhost.xml" file located @ FMS_Install_Folder/conf/_defaultRoot_/_defaultVHost_/ folder, named MaxConnection, check for its value that is set in your case

            <!-- Max number of clients that can connect to this vhost when running as local.  -->
            <!-- enforced by License key -->
            <MaxConnections>-1</MaxConnections>

    5. If you are using edge/origin based infrasstructure, then I will like to know if this connection rejection happens at edge livel or orgin level.

    6. Also, let me know if you are using server-to-server connections.

    7. Inside application.xml there is a connection tag having a maximum timeout value, please also make sure this value is correctly set:

            <Connections>
                <!-- Specifies max time (in secs.) that a transfer can take to   -->
                <!-- complete. Default is 60 secs. Since operations such as DNS  -->
                <!-- lookups may take some time, setting this to a low value     -->
                <!-- runs the risk of aborting perfectly normal operations.      -->
                <MaxTimeout>60</MaxTimeout>

    8. Also, let me know when a user failed to login then all the subserquent user start failing to login or it allows few of the user sometimes and rejects for few of the user some other time.

    9. It will help you if you can try to log info.description value whenever a NetConnection.Connect.Failed event occurs.

    Thanks!!

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