Forwarder Release Notes

All dependencies of the Forwarder are up-to-date and free of vulnerabilities as of the release date.

Issue related to releasing runtime channels during artifact uploads to Intelligence Cloud. Previously, this led to the channel being closed unexpectedly, even if it was in use by another process at the time. This fix ensures that the connection/channel remains available for sharing and reuse as intended.

All dependencies of the Forwarder are up-to-date and free of vulnerabilities as of the release date.

A custom header x-forwarder-time is added into every proxied request directed to Intelligence Cloud, serving as an indication of the time when the Forwarder proxies VM requests to Intelligence Cloud.

Network communication management between the Forwarder and the VM is improved. Robust network problem handling and comprehensive exchange of detailed information from the Forwarder to the VM has been implemented.

The communication state logged on the VM side now contains this information:

 
[CRS.connection][warning] Request postEventBatch failed on attempt 1 of 3,
elapsed (4,361 ms): code= 502, message=Bad Gateway, payload=null, error=[Forwarder]
The channel for uploading the artifact to Azul Intelligence Cloud has become inactive

This contains more detailed information, compared to the log message in earlier versions of the Forwarder:

 
[CRS.connection][warning] Request postEventBatch failed on attempt 1 of 3,
elapsed (4,361 ms): java.net.SocketException: Unexpected end of file from server

The maximum length of the response content that Intelligence Cloud can send to the VM is increased from 64KB to 512KB. Additionally, you can configure the maximum size of response data that the Forwarder may forward to the Runtimes, thus minimizing potential impact.

See for more details Forwarder Configuring Options.

An issue is fixed where the system lacked the capability to effectively manage certificate-related issues arising from the expiration of the Forwarder certificate. In some cases, such as PC hibernation, the scheduled task of re-issuing the certificate was not executed, resulting in the VM rejecting the SSL handshake, despite the Forwarder functioning properly.

Fixed a performance issue with the connection pool used to connect to the cloud:

The issue occurred when two or more threads attempted to establish a connection to the cloud simultaneously, with distinct index values. One thread was required to wait for the other, even though it was unnecessary, resulting in a delay. This unnecessary wait has been eliminated.

Resolved the problem resulting in a truncated response on the client side, which was caused by an incorrect value in the "Content-length" header when proxied by the Forwarder.

All dependencies of the Forwarder are up-to-date and free of vulnerabilities as of the release date.

Resolved an inconsistent state between the Forwarder state and the detailed metrics utilized for the computation of the state.

Enhanced the Forwarder’s functionality by adding comprehensive explanations in case the Forwarder state is not Green, enabling users to identify and address any issues with greater accuracy.

See Status API for an example.

Resolved an issue concerning the retain/release of HTTP messages that were proxied by the Forwarder, which had the potential to result in memory leaks.

Implemented the feature to periodically monitor and store the status of the Forwarder to a file.

See Forwarder Configuring Options for more information.

Fixed issue with duplicate proxied requests.

Fixed IOException: Premature close → channelClosed on Forwarder.

Improved error handling and permissions.

Minimise the number of Forwarder dependencies.

Added the ability to define the log level when starting the Forwarder using three different ways: via properties file, system variable or environment variable.

Fixed format of the Forwarder’s uptime. Added the ability to request extended statistics that include memory and CPU consumption.

Added homepage to the Forwarder when opening the root endpoint.

Simplification of the Forwarder authorization process.

Private key regeneration of the certificate on the Forwarder side during the daily certificate renewal process.

Added the ability to trust certificates issued to Azul by Amazon’s CA when the Forwarder connects to Azul Intelligence Cloud cloud.

No need to manually manage the certificates issued to the Forwarder.