/
Known Issues

Known Issues

In MediationZone 9.0, there are the following known issues:

See Fixed Known Issues for information about known issues that have been fixed since the release of 9.0.0.0.

Installation issues

Unable to change platform database after installation

It is not possible to change platform database after the installation is completed which used to be a feature that available since 8.x. This issue will be fixed in future releases.

Installation isn't possible if MZ_HOME path contains a folder name with spaces

If the MZ_HOME path contains and spaces the installation will fail. Please ensure the MZ_HOME doesn't contain any spaces prior to installing.

Installation reported as successful even if the platform fails to start

In some circumstances during installation the installer may report as successful when the platform has not started.

Warning messages displayed during installation

When the user performs “setup.sh prepare”, a warning message “setSecurityManager will be removed in a future release" is displayed. This does not impact functionality of MZ 9 installation and will be handled in future versions of MZ.

Error Occurs When Performing Multiple Installations on a Host with Different UNIX User IDs

The /tmp/syslog/syslog-debug.log file is created when a host machine contains an MZ 9 installation. This file will be overwritten by any subsequent MZ 9 installations that are performed on the same host machine with a different UNIX user ID. However, the attempt to overwrite this file will fail and cause errors to the subsequent installations.

To solve this issue, modify the platform.xml file setting by using the mzsh topo open platform command. Edit the platform.xml file, and change the directory to use another directory using the following command: <property name="mz.syslog.debuglogfile.filedir" value="[the directory]"/>.

Latest Oracle JDBC Driver Versions not Supported

Latest Oracle JDBC drivers such as version 21c and 23c are not supported in this release. Ensure to check the System Requirements for information about supported Oracle version.

Configuration History Loss After Upgrade from MediationZone 8

After upgrading from MediationZone 8, existing configuration history will no longer be available. This issue will be fixed in future releases.

Deleted Configuration History Unavailable After Upgrade from MediationZone 8

After upgrading from MediationZone 8, previously deleted configuration history in MediationZone 8 is no longer accessible in the Configuration Tracer. This issue will be fixed in future releases.

Only the first EC is started when multiple ECs are specified

When specifying multiple ECs during installation using a comma-delimited format (e.g., ec1,ec2,ec3), the installation completes successfully. However, only the first EC (ec1) is started post-installation. The remaining ECs are not started as expected.

Upgrade issues

Legacy Desktop launcher does not launch desktop when install.security is changed during upgrade

When the user with an existing installation has install.security set to false when installation was performed. When upgrading to version 9.x, the upgrade will set the install.security to true by default. This will result in an issue where one the upgrade is complete, the Legacy Desktop launcher will not launch the desktop and will instead have an error message say that it failed to retrieve binary data. If your existing installation was installed with install.security set to false, ensure that the install.security is set to false in the install.xml before performing the upgrade.

Unable to Upgrade When Using a Symbolic Link as MZ_HOME

Users are encountering issues with symlinks when using them as MZ_HOME during an installation or upgrade due to the java.nio.file.FileAlreadyExistsException error.

This issue arises from a bug reported under [JDK-8294193] Files.createDirectories throws FileAlreadyExistsException for a symbolic link whose target is an existing directory - Java Bug System (openjdk.org) and has been fixed in JDK 20.

To avoid encountering this error during installation or upgrade, you should use an absolute path instead of a symlink for the MZ_HOME directory.

Removing Unused Service Contexts After Upgrading from MediationZone 8

When upgrading from MediationZone 8 to MediationZone 9, all picos are upgraded resulting in an installation with numerous unused service contexts that should be removed.

To resolve this, you are required to use the mzsh topo command to manually remove these picos. For more information on the steps, refer to Removing Pico Configurations.

 

User Interface issues

New desktop issues

Database Agent Assignment Tab Value Are Not Cleared

When Value Type is set to "To UDR" or "NULL", the Value column are not cleared.

Database Agent MIM Browser Need To Click Twice To Close It

The MIM browser open from database agent, need to close it by hitting twice on cancel button or the X button to close it.

External Reference Profile Datalist Can Be Altered in Read-Only Mode

When certain procedures are made, it is possible to alter the data list found in the external reference profile while the read-only mode is used. This causes a system-wide DRRCPException to be thrown.

Login Web UI Will Go To Last Page That Last User Accessed 

When User A logs out from web UI, and User B logs in, it will automatically go to the page last accessed by User A.

Integer field validation can be broken

Inputting integer values outside of the expected range can break the validation in the UI.

Changing LDAP-agent settings on the Desktop messes up workflow in the Legacy Desktop

Creating workflows with the LDAP agent breaks down the routes when saved using the Desktop interface and opened with the Legacy Interface.

Type Assigned indication not shown in MIM browser

This can be viewed on the Legacy desktop if required.

New profile becomes read-only on save

When creating a new profile as soon as it is saved it becomes read-only. The user needs to click the edit button in order to continue editing.

Aggregation Inspector pagination fails on very large files

With particularly large files the Aggregation Inspector will not scroll through all results. Users will need to use the Legacy Desktop in these cases.

Idle timeout only warns the user once

Inactive users will be logged out after a configurable period, following a warning to that effect. If a user is active after the warning they won't be logged out, but if they are inactive again then they will be logged out with no warning. 

Cannot log in to multiple platforms

It is not currently possible to log in to multiple separate platforms using the new UI in one browser. Users can use different browsers, incognito modes, or the Legacy Desktop if this is required.

Null Pointer Exception when updating password with enhanced security enabled on the new desktop

When you install the Platform with the following properties set to true:

  • mz.security.user.control.enabled

  • mz.security.user.password.reset.enabled

When logging in for the first time, a prompt to update the password will occur. When logging in for the first time on the new desktop, attempting to update the password will lead to a Null Pointer Exception. It is recommended to log onto the legacy desktop first to update the password for the account first before logging into the new desktop.

Accessibility Issues

The new web-native desktop aims to be fully accessible, but there are currently some outstanding issues regarding this. These include:

  • In some interfaces, the keyboard navigation doesn't follow the ideal order or convention

  • Some icons have unnecessary alt text

  • Some checkboxes are not correctly labelled

  • Failure messages, for example on failed login, don't have clear enough contrast