Overview

After upgrading your Java, you might need to update your JAVA_HOME path settings manually. If the JAVA_HOME path is not updated correctly your Filters might not work correctly (ElasticSearch depends on Java), or during a FogBugz reinstall or upgrade you might face errors.

Solution

Verify your configured Java version

Verify using the Windows Command Console (CMD) the Java version configured as System Environment Variable. Run the following command.
ECHO %JAVA_HOME%

The system retrieves the path to the latest Java Developer Kit version installed. If the upgrade was correctly installed, for example, for FogBugz 8.22.x, the path indicates the version jdk1.8.0_162, which is the latest version packed with FogBugz 8.22.x.
Check the value of the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\FogBugz ElasticSearch\Parameters\Java

If the value of the Jvm key, as shown in the image above, shows a different java version than the version you received in step 1, then it will result in your Filters and Searches failing, because ElasticSearch will stop working after the upgrade

In our example, the version mentioned in the Jvm key is jdk1.7.0_80, which does not match with the version seen in step 1.

Update your Java configuration settings

Copy the value of the Java version obtained in Step 1 of the verify process. In our example, it is jdk1.8.0_162.
Replace the Java version in the Jvm key with this version value, as shown in the image below.
Restart the FogBugz ElasticSearch service.

Testing

Log out from FogBugz and then log back in to reload the site. Now try accessing the case listing in FogBugz, and it should start showing filters, case listing, and searches without any error.

Back to the top