{"id":5236,"date":"2018-09-03T21:43:01","date_gmt":"2018-09-04T04:43:01","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=5236"},"modified":"2018-09-03T21:43:01","modified_gmt":"2018-09-04T04:43:01","slug":"run-java-exe-from-path","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/run-java-exe-from-path\/","title":{"rendered":"Q & A: How do I get AlwaysUp to run Java.exe in the PATH?"},"content":{"rendered":"
\"Q<\/div>\n
\n  I run a Java program EchoLink Proxy<\/a> as part of Ham Radio networking. A routine update replaced the Java folder with its new version number thus my AlwaysUp Application field to run the program needed manual edit from:<\/p>\n

C:\\Program Files (x86)\\Java\\jre1.8.0_171\\bin\\java.exe<\/p><\/blockquote>\n

to<\/p>\n

C:\\Program Files (x86)\\Java\\jre1.8.0_181\\bin\\java.exe<\/p><\/blockquote>\n

I tried simply providing “Java.exe” (which works from a CMD prompt) but AlwaysUp requires the full-path. How can I get AlwaysUp to run the Java.exe in my PATH environment variable?<\/p>\n

— Anonymous<\/p>\n<\/div>\n

Hi. AlwaysUp expects a full path, so I see the problem!<\/p>\n

We recommend adding a “layer of indirection” to solve the problem. Please:<\/p>\n

    \n
  1. \n

    \nCreate a new Windows batch file that runs your full java command line. However, instead of specifying the full path to java, simply use java.exe<\/b>.\n<\/p>\n

    \nWhen run, the batch file will use whatever java.exe<\/b> is in your Windows account’s PATH variable.\n<\/p>\n

    \nHere is what our simple batch file (saved to “C:\\Tools\\start-java-app.bat”) looks like:\n<\/p>\n

  2. \n

    \nUpdate your AlwaysUp entry to run the new batch file. Specify the full path to the batch file in the Application<\/b> field on the General<\/b> tab:\n<\/p>\n

  3. \n

    \nAnd on the AlwaysUp Logon<\/b> tab, specify the Windows account you are logged in to right now. Java must be launched in this account so that it finds the correct PATH environment value.\n<\/p>\n

  4. \n

    \nFinally, update the new batch file to add a 5 second delay at the end. We recommend using the Windows TIMEOUT command<\/a>, but there are several alternatives<\/a>:\n<\/p>\n

    timeout \/t 5<\/b><\/p><\/blockquote>\n

    \nWithout this adjustment, the batch file may exit very quickly and fool AlwaysUp into thinking that the batch file failed to start properly.\n<\/p>\n

    \"Add<\/a><\/div>\n<\/li>\n
  5. \n

    \nSave your batch file — and your settings in AlwaysUp.\n<\/p>\n<\/li>\n<\/ol>\n

    \nNow, when you start your modified entry from AlwaysUp, the following will happen:\n<\/p>\n

      \n
    1. \n

      AlwaysUp will start the batch file<\/p>\n<\/li>\n

    2. \n

      The batch file will launch Java from the PATH, as you have configured<\/p>\n<\/li>\n

    3. \n

      The batch file will “sleep” for 5 seconds<\/p>\n<\/li>\n

    4. \n

      The batch file will exit<\/p>\n<\/li>\n

    5. \n

      AlwaysUp will notice that the batch file has exited and “attach” to the Java.exe child process<\/p>\n<\/li>\n

    6. \n

      AlwaysUp will continue to monitor Java.exe and restart it (via the batch file) if it ever crashes\/fails\/exits.<\/p>\n<\/li>\n<\/ol>\n

      \nAny monitoring, reporting and alerts you have configured should continue to work as they did before.\n<\/p>\n

      \nPlease let us know<\/a> if you run into any trouble implementing this approach!<\/p>\n