How to Run a Weave Hotfix

Owned by Lucy Minato (Deactivated)
Last updated: 24 Apr, 2024 by Shaun Forbes
2 min read

If you already have a version of Weave running and have encountered a problem, you may be asked to run a "hotfix" if it's been determined that your issue has already been fixed and was released as part of a hotfix. A hotfix contains one or more bug fixes that have been found since the last release. 

Running a hotfix is similar to running a Weave update; the steps to follow are provided below.

(warning) This page is valid if you are already running a 2.5 or later version of Weave. 

Step-by-step guide

  1. Download the hotfix from the link provided in your support ticket or from the Weave download page (in the Hotfixes section, choose the hotfix for the version of Weave you are running).
  2. Stop the existing Weave service. 
  3. Delete your weave.log (..\weave\logs) file so you can start with a clean log file for the hotfix testing. 
  4. Optionally make a backup of Weave plugins and features folders (in case you need to roll-back to your original Weave). The hotfix will just replace the files in the folders it needs to update.
  5. Then either
    1. Run the hotfix jar file without any extra parameters and I'll work the same way as the Weave installer and you have to choose the current Weave directory, e.g.
      java -jar c:\downloads\weave-hotfix-2.6.2.3.jar

      Or:
    2. Run it with the existing Weave directory as a command line parameter and it'll run, update the directory and exit without any interaction.
      java -jar c:\downloads\weave-hotfix-2.6.2.3.jar c:\weave-2.6.2-dev

      If you don't have java installed on the server then you'll need to use Weave's own java to run the hotfix so it'll be something like:
      cd c:\weave-2.6.2-dev\jre\bin
      java -jar c:\downloads\weave-hotfix-2.6.2.3.jar c:\weave-2.6.2-dev
  6. Restart your Weave service and test the fix.


It's best to apply the hotfix to your Weave development environment (DEV) and test it, before applying to your Weave production environment (PROD) but generally hotfixes are minor changes and just update one or two files in the plugins directory.


The best practice to adopt for hotfixes is to apply them when they are released for the version you are running. Hotfixes are generally small fixes and you’ll generally be better off when you install them.

The fixes provided in each hotfix are documented on the What’s New page.