top of page


WAARP news

WAARP R66 3.5.0

Selection of listening interfaces, reduction of memory footprint, etc.

Waarp R66 Update Release Notes

To begin with, version 3.5.0 of the Waarp R66 update is mainly a corrective version, it therefore brings many internal improvements which therefore reduce the memory footprint of Waarp R66 servers significantly.

In addition, this update also brings the possibility of configuring the listening interfaces for transfers (in clear and in TLS) but also the monitoring and administration interfaces. Also, the REST API listening interface was already configurable.

Configuring listening interfaces

Previously, the REST API server integrated into Waarp R66 already made it possible to configure the listening interface by specifying the IP address to use.

From now on, this is also the case for transfer services (R66 protocol in the clear and in TLS) as well as for the HTTP interfaces for monitoring transfers and the HTTPS administration interface, notably with the introduction of four new options. configuration in the block.

Among them :

  • serveraddresses: Addresses used for the R66 protocol

  • serverssladdresses: Addresses used for the R66 protocol in TLS

  • serverhttpaddresses: Addresses used for the supervision web interface

  • serverhttpsaddresses: Addresses used for the HTTPS administrative web interface

Thus, for each of these tags, it is possible to specify several addresses, separated by commas. By default, all interfaces are listened to.

List of changes

What's new in the Waarp R66 update

First, here are the few new features applying to the MAJ:

  • [ #74 ] Network interfaces are configurable in addition to the port to use. Thus, several interfaces are possible (separated by a comma).

Waarp R66 Update Fixes

Then, here are now all the fixes made compared to the old version of the update:

  • [ #77 ] First of all, the risk of direct memory capacity overflow is greatly reduced in favor of the use of the Netty Memory Pool within the JVM. Then, major optimizations in terms of allocations/deallocations were also carried out.

  • [ #72 ] Then, the command could be blocked in certain cases. (issue #65 )

  • [ #71 ] Moreover, XMLRuleDAO did not take transfer rules into account (case of a client without a base like FileMonitor) (issue #64 )

  • [ #69 ] Actions in the System menu of the administration interface were missing. (issue #63 )

  • [ #70 ] A transfer from a client to itself (self-transfer) caused the transfer to be deleted. (issue #62 )

  • [ #68 ] Additionally, the admin web page was broken with maps in the Transfer Information field. (issue #61 )

  • [ #67 ] Finally, the output options (csv, xml, json, property) are restored and in an appropriate format. (issue #60 , issue #78 )

  • [ #66 ] Finally, EXECOUTPUT caused a class mapping error (issue #59 )

  • Code cleanup (styles)

  • Updating dependencies

  • Packaging: Changes to Java's Xms and Xmx values with recommended values.

  • Packaging: Correction of transfer launch commands under Windows

  • Packaging: Fixed stopping of filewatchers and R66 servers

  • Packaging: .deb packages now depend directly on Java 8 (and not the default JRE).

  • Packaging: Fixed errors “The %1 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. » when starting services on some versions of Windows.

  • Packaging: by default, R66 client logs are written to files rather than to standard output.


Finally, this new version of the R66 update is completely compatible with versions 3.x and does not require any special handling to optimize it.

The standard procedure can be followed for this update.


Also, find some resource links below:


bottom of page