Chapter 2. MTA 7.2.3

MTA creates resources with auto-assigned IDs after creating RESTful resources with specific IDs

Previously in MTA, when a resource was created with a specific ID through a REST call, after which another resource was created with an auto-assigned ID, either through a REST call or in the user interface, an http-409 conflict could occur. This issue has been resolved in MTA 7.2.3. (MTA-5288)

MTA now runs Java rules when analyzing Java binaries on Microsoft Windows

Previously, when you performed a containerless analysis of compiled Java applications using Microsoft Windows, MTA did not match a Java rule and generated a Java Model (code 969) error. As a result, some rules did not trigger issues in the analysis report. This issue has been resolved in MTA 7.2.3. (MTA-5370)

Resources and limits now present on all pods

In MTA 7.2.3, all pods created by the mta-operator and the pod for the operator have resource limits and requests set. This way they also work in an environment where resource limits and requests are required, for example, when a project has resource quotas defined. (MTA-5406)

Running analysis on large .EAR binary filesobtains differents results

When analyzing binary applications, MTA relies on Maven search index to determine whether dependencies are internal to the application or whether the application is installed as an open-source dependency. Depending on the availability of the Maven search index, it is assumed that an open-source dependency is internal to the application and includes the dependency in the analysis results. In this case, analysis returns more incidents and greater effort to address issues found in dependencies, even if the user does not expect to see those results.

MTA CLI generates a process error in log after Java binary analysis using Microsoft Windows

When you analyze Java binaries using Microsoft Windows, MTA CLI generates a process error when deleting files in the exploded directory after moving the decompiled files to the Java project path. This error does not affect the analysis results. Currently, there is no workaround for this issue. (MTA-5355)

MTA CLI analysis can take a long time for multi-module binaries when dependency resolution fails

When you analyze multi-module binaries in MTA CLI, the analysis can take a long time to complete if dependency resolution fails. Currently, there is no workaround for this issue. (MTA-5398)