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.
This page is valid if you are already running a 2.5 version of Weave.
Step-by-step guide
- Download the hotfix from the link provided in your support ticket or from the Weave download page.
- It's best to apply the hotfix to your Weave development environment (DEV) and test it, before applying to your Weave production environment (PROD).
- Stop the existing Weave DEV service.
- Delete your
weave.log (..\weave\logs)file so you can start with a clean log file for the hotfix testing. - Make a backup of Weave DEV folder (in case you need to roll-back to your original Weave DEV). The hotfix will just write over the files in the folders it needs to update.
- Then either
- 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.5.21.9.jar
Or: - 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.5.21.9.jar c:\weave-2-5-21-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-5-21-dev\jre\binjava -jar c:\downloads\weave-hotfix-2.5.21.9.jar c:\weave-2-5-21-dev
- 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.
- Restart your Weave DEV service and test the fix.
For information on pending releases, refer to Pending Release page.
Related articles