Hotfixes

The following hotfix is available for Appian 19.4.

Hotfix Package B

This is a cumulative hotfix package that includes Hotfix Package A as well as new hotfixes in a single download and a set of instructions. This package is required for any Appian 19.4 installations not currently on Hotfix Package B. After installing, you will be running on Appian 19.4 Hotfix Package B.

See the Installation section at the bottom of this page for instructions on how to install this hotfix package.

19.4 Hotfix Package B

Release Date: 13 December 2019

Resolved Issues

  • Security Updates - High

  • AN-145504 - Critical
    For security reasons, the Query DB Node smart service has been updated. Customers running the LOAD DATA INFILE command against a MySQL instance (only applicable to Configured Data Sources; not applicable to the Appian Cloud database) from a Query DB Node in a Process Model must set the conf.data.load.infile.paths custom property as a comma-separated list of file paths to whitelist the required directories. If the property is not set, any Process Model using this command will pause by exception at runtime. This command is generally used to periodically load data from files into the database, and so we expect that most customers will not have to take the required action described here.

  • AN-146029 - High
    Fixed an issue that caused the username field on the Forgot Password page to be auto-capitalized.

  • AN-146210 - High
    Saving user filters is now visible on all record types.

  • AN-146412 - High
    Clicking on a start process link after the SAIL cache is full no longer results in a full-screen error.

  • AN-147053 - High
    A memory leak in service manager has been resolved.

  • AN-145522 - Medium
    A stability fix for service manager in the case of an unstable or degraded zookeeper cluster.

  • AN-145736 - Medium
    The service manager process is now more robust to leadership changes during the startup process.

  • AN-146140 - Medium
    An error retrieving document statistics on highly-available installations has been resolved.

  • AN-145712 - Medium
    Fixed an issue with the Dynamics connected system that prevented creating or updating entity records with lookup fields.

  • AN-147070 - Medium
    Fixed an issue that prevented failed Health Check runs from being properly recorded.

  • AN-147232 - Medium
    Reduces the number of messages broadcast between app servers, resulting in a performance improvement in the engines.

  • AN-141142 - Low
    The service manager process is now robust to multiple copies of the same engine running when only one is configured.

  • AN-146167 - Low
    Fixed an issue where engine_disk_usage.csv was not logging accurate values for some directories

  • AN-146705 - Low
    Fixed an issue causing Search Server to break a site that is low on disk space

Release Date: 22 November 2019 (Released as Hotfix Package A)

Resolved Issues

  • Security Updates - Critical

  • AN-144440 - High
    A race condition in service manager that could lead to site unavailability has been resolved.

  • AN-139947 - Medium
    System memory use for Appian Cloud sites has been reduced.

  • AN-144781 - Low
    The accent color is now correctly applied to all links in Tempo.

  • AN-145596 - Low
    Stability improvement for service manager component.

Installation

Perform the following steps to apply the hotfix:

  1. Stop Appian. See Starting and Stopping Appian for detailed instructions:
    1. Shut down the application server.
    2. Shut down the search server.
    3. Shut down the data server.
    4. Shutdown all Appian Engines, ensuring that the engines are checkpointed upon shutdown.
  2. Back up your existing Appian instance. See Backing Up Your Existing Appian Instance for instructions.
  3. Unzip the contents of the 19.4.0.0_Hotfix_Package_B.zip archive into your <APPIAN_HOME> directory.
  4. Run the deleteFiles script (deleteFiles.bat on Windows, deleteFiles.sh on Linux) that is now located in your <APPIAN_HOME> directory.
    • If the script reports that some files were not deleted, address the reason for the failure (common causes listed below), and run it again until it no longer reports failed deletions.
    • Common causes of failed file deletion include:
    • The file is open in another window or process
    • The file is locked
    • You do not have permission to delete the file
  5. Unzip the contents of the updates.zip archive that is now located your <APPIAN_HOME> directory.
  6. Run the installJdk script (installJdk.bat on Windows, installJdk.sh on Linux).
  7. If you maintain customized or overridden Spring Security .xml files, merge them with the associated base files in the /deployment/web.war/WEB-INF/conf/security/ directory.
  8. Delete the deleteFiles scripts, the installJdk scripts, the OpenJDK .tar.gz and .zip files, and updates.zip.
  9. If you are using a Web server, copy the content of <APPIAN_HOME>/deployment/web.war to the folder where the Web server is getting the static resources. See Copy Static Resources to the Web Server for more information.
  10. Run the configure script to deploy your environment's configuration and re-configure any node names previously set by the configure script tools.
  11. Start Appian:
    1. Start the Appian Engines.
    2. Start the data server.
    3. Start the search server.
    4. Start the application server.

To determine if Appian 19.4 Hotfix Package B is deployed, open the build.info file located in <APPIAN_HOME>/conf/. The contents of this file should match the following code sample:

build.revision=cb1e6f30703da3a4533146fbe6782f49036bf1ce
build.version=19.4.54.0
FEEDBACK