Known Issues
...
1.0.
...
23 (10/31/2024)
FLEXDEPLOY-12786 - The installer now works with newer 8.0 and 9.0 versions of the docker image. Previously it failed with error message Failed to register in JMX: [javax.naming.NamingException: Unexpected exception resolving reference [Root exception is java.lang.NumberFormatException: For input string: "${MAX_ACTIVE_CONNECTIONS}"]
1.0.22 (10/10/2024)
FLEXDEPLOY-12825 - When you change the Java location in the installer’s config file, it now properly updates the java path in your setenvoverride.sh file.
1.0.21 (9/13/24)
FLEXDEPLOY-12704 - FlexDeploy 9.0 compatibility. FlexDeploy 9.0 must be installed with version 1.0.21 or higher. 1.0.21 also works with older versions of FlexDeploy.
1.0.20 (6/24/24)
FLEXDEPLOY-12432 - The Java Version check now works when _JAVA_OPTIONS are set.
1.0.19 (5/28/24)
FLEXDEPLOY-12312 - Resolved the 1.0.18 regression where installing with maintain set to 1 didn't start the new config files with the appropriate values.
1.0.18 (4/5/24)
FLEXDEPLOY-11883 - Resolved regression 11883 in installer 1.0.17 where the installer was requiring a JDK when a JRE may be sufficient.
FLEXDEPLOY-11617 - The installer now sets up influx more completely before starting FlexDeploy. This should reduce instances of customers upgrading and not getting influx setup because they cancel the installer before it completes.
FLEXDEPLOY-11887 - The installer no longer modifies the context or server xml files at all when maintain is set to 1. Previously, the database url, port, and password were updated, which caused issues for customers using Cyberark and other password management tools.
1.0.17 (3/12/24)
Known Issues
Installer 1.0.17 does not work with JRE. If you are using a JRE, do not use version 1.0.17.
FLEXDEPLOY-11081 - The installer now verifies that the Java version is at least 8.0.192.
...