{"id":5252,"date":"2019-03-26T07:52:59","date_gmt":"2019-03-26T14:52:59","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=5252"},"modified":"2019-03-26T07:52:59","modified_gmt":"2019-03-26T14:52:59","slug":"multiple-alpha-servers","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/multiple-alpha-servers\/","title":{"rendered":"Q & A: How do I Prevent Multiple Alpha Application Servers from Running?"},"content":{"rendered":"
\"Q<\/div>\n
\n  I am using AlwaysUp to control my Alpha Anywhere Application Server<\/a>. I have noticed that if I go to Task Manager that I would sometimes have more than one instance of AlphaFive running under processes. Would you perhaps have any idea how to prevent this?<\/p>\n

— John, TM Software<\/p>\n<\/div>\n

Hi John. We have a couple of recommendations:<\/p>\n

1.  Have AlwaysUp stop all other copies of Alpha<\/h2>\n

First, since you only want a single copy of Alpha Anywhere Application Server running at any time, you should check these boxes on the Startup<\/b> tab:<\/p>\n

\"AlwaysUp<\/a><\/div>\n

With those options enabled, AlwaysUp will perform the following steps whenever it determines that Alpha needs to be started:<\/p>\n

    \n
  1. \n

    Scan the system’s processes for all instances of A5ApplicationServer.exe<\/b>, the Alpha Anywhere Application Server executable.<\/p>\n<\/li>\n

  2. \n

    \nIf any matching processes are found:<\/p>\n

      \n
    1. \n

      Attempt to stop each one gracefully<\/p>\n<\/li>\n

    2. \n

      Wait a few seconds for them all to exit<\/p>\n<\/li>\n

    3. \n

      Forcibly terminate any that remain<\/p>\n<\/li>\n<\/ol>\n<\/li>\n

    4. \n

      Launch Alpha server, as configured.<\/p>\n<\/li>\n<\/ol>\n

      This process guarantees that the instance of Alpha Anywhere launched by AlwaysUp will be the only one running — ensuring that your web server gets all the ports (and other resources) it needs at startup.<\/p>\n

      But while this approach effectively “clears the stage” for AlwaysUp, it will not prevent a second instance of Alpha from starting after<\/i> the AlwaysUp-controlled instance is running. You may still see multiple copies of Alpha in Task Manager.<\/p>\n

      This brings us to our second recommendation…<\/p>\n

      2.  Don’t start Alpha automatically outside of AlwaysUp<\/h2>\n

      Is Alpha Anywhere Server being started outside of AlwaysUp? In particular:<\/p>\n