Overview

Users of AureaMonitor Intermediary for release 2023 R2 and R3 may encounter an issue with the new REST WADL validation, which does not work for all WADL. This problem specifically affects new REST SG. The root cause is a change in the host where the WADL schema was stored. Previously, it was accessible via HTTP, but it now redirects to HTTPS, and the system's logic did not account for this redirection.

Solution

To resolve this issue, follow these steps:

1. Add the Java property "com.actional.intermediary.rest.validateWADL=false" to the AI profile JVM argument list. This will disable the WADL validation that is causing the issue.
2. Alternatively, you can use the 2023 R1 version of the software, which does not have this issue.

Our development team is working to permanently fix this issue, which will be released in the next version of the software.

Summary

This article provides a solution to the issue with the AureaMonitor Intermediary for release 2023 R2 and R3, where the new REST WADL validation does not work for all WADL due to a change in the host where the WADL schema was stored.

FAQ

1. What is the root cause of this issue?
   The root cause is a change in the host where the WADL schema was stored. Previously, it was accessible via HTTP, but it now redirects to HTTPS, and the system's logic did not account for this redirection.
2. What is the workaround for this issue?
   The workaround is to add the Java property "com.actional.intermediary.rest.validateWADL=false" to the AI profile JVM argument list or to use the 2023 R1 version of the software.
3. Is there a permanent fix for this issue?
   Our development team is working on a permanent fix, which will be released in the next version of the software.