9. Release Notes¶
9.1. Supported Platforms¶
RTI Web Integration Service is supported on the platforms in Table 9.1.
Operating System |
Version and CPU |
---|---|
Linux® (Intel® CPU) |
All Linux platforms on x64 CPUs in the RTI Connext DDS Core Libraries Release Notes for the same version number. |
Linux (Arm® CPU) |
Ubuntu® 18.04 and 22.04 LTS on Arm v8 CPUs. |
macOS® |
All macOS platforms in the RTI Connext DDS Core Libraries Release Notes with the same version number. |
Windows® |
All Windows platforms in the RTI Connext DDS Core Libraries Release Notes for the same version number. |
Note: POSIX®-compliant architectures that end with “FACE_GP” are not supported.
Web Integration Service is also supported on the platform in Table 9.2; this is a target platforms for which RTI offers custom support. If you are interested in this platform, please contact your local RTI representative or email sales@rti.com.
Operating System |
Version and CPU |
---|---|
Linux |
Yocto Project® 2.5 on Arm v8 |
9.2. Compatibility¶
For backward compatibility information between Web Integration Service 6.1.2 and previous releases, please see the Migration Guide on the RTI Community portal.
9.3. What’s New in 6.1.2¶
9.3.1. New platforms¶
Web Integration Service is supported on these new platforms:
Operating System |
Version and CPU |
---|---|
Linux |
Ubuntu 22.04 on Arm v8 |
Ubuntu 22.04 on x64 |
|
macOS |
macOS 12 on x64 |
QNX |
QNX Neutrino 7.1 on x64 |
QNX Neutrino 7.1 on Arm v8 |
|
Windows |
Windows 11 with Visual Studio on x64 |
For details on these platforms, see the RTI Connext DDS Core Libraries Platform Notes for this release.
9.3.2. Third-party software upgrades¶
The following third-party software used by Web Integration Service has been upgraded:
Third-Party Software |
Previous Version |
Current Version |
---|---|---|
SQLite® |
3.37.2 |
3.39.4 |
For information on third-party software used by Connext DDS products,
see the “3rdPartySoftware” documents in your installation:
<NDDSHOME>/doc/manuals/connext_dds_professional/release_notes_3rdparty
.
9.4. What’s Fixed in 6.1.2¶
9.4.1. Version number not displayed¶
Web Integration Service did not show its version number at startup or when using the -version option. This problem has been resolved.
[RTI Issue ID WEBINT-249]
9.5. Previous Releases¶
9.5.1. What’s new in 6.1.1¶
9.5.1.1. New platforms¶
macOS 11 (Big Sur) (Arm v8)
macOS 11 (Big Sur) (x64)
This release has validated that the libraries for architecture x64Darwin17clang9.0 can also be used on macOS 11 (Big Sur) systems with x64 CPUs.
For more information on these platforms, see the RTI Connext DDS Core Libraries Platform Notes for this release.
9.5.1.2. Third-party software upgrades¶
The following third-party software used by Web Integration Service has been upgraded:
Third-Party Software |
Previous Version |
Current Version |
---|---|---|
Bootstrap |
3.3.6 |
5.1.3 |
CivetWeb |
1.13 |
1.15 |
JQuery® |
1.12.3 |
3.6.0 |
OpenSSL® |
1.1.1k |
1.1.1n |
SQLite® |
3.29.0 |
3.37.2 |
Some of these upgrades may fix potential vulnerabilities. See Fixes related to vulnerabilities.
For information on third-party software used by Connext DDS products,
see the “3rdPartySoftware” documents in your installation:
<NDDSHOME>/doc/manuals/connext_dds_professional/release_notes_3rdparty
.
9.5.2. What’s fixed in 6.1.1¶
9.5.2.1. Malformed WebSocket handshake messages may have caused a segmentation fault¶
Web Integration Service’s WebSocket API requires client applications to initiate communication with a HELLO message, which provides all the necessary information to complete a handshake (e.g., content type, protocol version, and API keys). HELLO messages must be encoded as a colon-separated string of name-value pairs (each terminated by a carriage return and line-feed character sequence).
In Web Integration Service 6.1.0, a malformed HELLO message may have caused an unhandled error that lead to a crash in some cases. This issue has been resolved.
[RTI Issue ID WEBINT-208]
9.5.2.2. Race condition when closing WebSocket connection caused a segmentation fault¶
Web Integration Service’s WebSocket API requires a WebSocket connection. When that connection was bound to one or more data readers, there was a race condition if the connection was closed while Web Integration Service was sending a message to it. This caused the connection to be removed from the service’s memory, followed by a segmentation fault. This issue has been resolved.
[RTI Issue ID WEBINT-208]
9.5.3. What’s new in 6.1.0¶
9.5.3.1. New platforms¶
Web Integration Service now includes support for these platforms:
macOS 10.15 (x64)
Red Hat® Enterprise Linux 7.6 (x64)
Ubuntu 18.04 LTS (Arm v8)
Ubuntu 20.04 LTS (x64)
Yocto Project® 2.5 (Arm v8) (custom-supported target platform)
For more information on these platforms, see the RTI Connext DDS Core Libraries Platform Notes for this release.
9.5.3.2. Removed platforms¶
These platforms are no longer supported:
32-bit Linux and Windows platforms
macOS 10.12
SUSE Linux Enterprise Server 11
Ubuntu 12.04 LTS
9.5.3.3. Support for WebSockets¶
This release introduces support for WebSockets (WS) and Secure WebSockets (WSS) in Web Integration Service, so it will allow web applications to interact through these protocol in a DDS environment. For more information, see WebSocket API.
9.5.3.4. Upgraded to CivetWeb v1.13¶
Web Integration Service has upgraded the version of its embedded web server, CivetWeb, to v1.13. For more information on CivetWeb, please see the Release Notes on GitHub: https://github.com/civetweb/civetweb/blob/master/RELEASE_NOTES.md#release-notes-v113.
9.6. Known Issues¶
9.6.1. Configurations and their applications cannot use same name¶
Due to current limitations in Connext DDS’s XML Parser, the name of the Web Integration Service configuration tag and the name of the applications within that configuration cannot be the same. For example:
<web_integration_service name="ShapesDemo">
<application name="ShapesDemo"/>
</web_integration_service>
To workaround this limitation, use different names for the service configuration tag and the applications within. For example:
<web_integration_service name="ShapesDemo">
<application name="ShapesDemoApplication"/>
</web_integration_service>
[RTI Issue ID CORE-3542]