New releases of cloud and fog are made available on a regular basis. This page lists all the bug fixes and changes in the different versions.
This article lists all the changes in Vortex Link
Please note that Vortex Link was previously Vortex Cloud and Vortex Fog. They have been merged into one product with the same feature set.
Release History
| Version | Date | Vortex Platforms Version |
|---|---|---|
| 3.0.4 | 2019-07-15 | Vortex 2.6.1 |
| 3.0.3 | 2019-07-09 | Vortex 2.6 |
| 3.0.2 | 2019-01-22 | Vortex 2.6.0 |
| 3.0.1 | 2018-06-07 | Vortex 2.6.0 - Vortex Link DDS Security release |
| 3.0.0 | 2018-04-05 | Vortex 2.6.0 - First release of Vortex Link |
| 2.1.4 | 2018-01-31 | Vortex 2.5.0 |
| 2.1.3 | 2017-11-03 | Vortex 2.4.2 |
| 2.1.2 | 2017-07-13 | Vortex V2.4.1 |
| 2.1.1 | 2017-03-27 | Vortex V2.4.1 |
| 2.1.0 | 2017-03-10 | Vortex V2.4 |
| 2.0.0 | 2016-09-22 | Vortex V2.3.0 |
| 1.3.2 | 2016-04-26 | Vortex V2.2.0 |
| 1.3.1 | 2016-02-17 | Vortex V2.1.0 |
| 1.3.0 | 2015-11-24 | Vortex V2.0.0 |
| 1.2.0 | 2015-03-09 | Vortex V1.2.0 |
| 1.1.0 | 2014-10-07 | Vortex V1.1.0 |
| 1.0.1 | 2014-08-01 | Vortex V1.0.1 |
| 1.0.0 | 2014-07-11 | Vortex V1.0.0 (first Cloud release) |
Fixed bugs and changes in Vortex Link
Version 3.0.4
| Report ID | Description |
|---|---|
| CLOUD-1225 | Fix NullPointerException and the random jenkins failing |
Version 3.0.3
| Report ID | Description |
|---|---|
| JMOB-1579 | Fix half disconnection syndrome and interoperate with ospl |
Version 3.0.2
| Report ID | Description |
|---|---|
| JMOB-1579 | Fix half disconnection syndrome |
Version 3.0.1
| Change ID | Description |
|---|---|
| CLOUD-1153 | Add support of DDS Security enabled Participants. The DDS Security authentication and cryptographic protocols are transparently routed by Link. See User Guide chapter "DDS Security" for more details |
Version 3.0.0
| Change ID | Description |
|---|---|
| CLOUD-1138 | Rebrand Vortex Cloud and Vortex Fog as a single product with the same features: Vortex Link. See User Guide and Migration Guide for more details. |
Fixed bugs and changes in Vortex Cloud and Fog
Version 2.1.4
| Change ID | Description |
|---|---|
| CLOUD-1134 | Add the "cloud.tcp.externalNetworkAddresses", "cloud.udp.externalNetworkAddresses", "fog.tcp.externalNetworkAddresses" and "fog.udp.externalNetworkAddresses" configuration options for finer tuning of the locators that are advertised to the other participants, depending the transport. See User Guide for more details |
Version 2.1.3
| Change Id | Description |
|---|---|
| CLOUD-1102 | All documentation have been updated for rebranding to ADLINK. |
| CLOUD-1113 | Added the cloud.participantsAdvertisement and fog.participantsAdvertisement configuration properties to force the advertisement of discovered Participants to the other Participants. See User Guide for more details |
| CLOUD-1091 | Fixed crash of Cloud and Fog services when the log level is configured to TRACE. |
Version 2.1.2
| Change ID | Description |
|---|---|
| CLOUD-1026 | In KeysManager, added the possibility to set a validity date when exporting a CRL. |
| CLOUD-1036 | In KeysManager, added a "--export" command line option to export a hierarchy without starting the GUI. |
| CLOUD-1044 | Fixed a security flaw that allowed restricted devices to connect any service. This flaw was introduced in Vortex Cloud and Fog 2.1.0 and still present in 2.1.1 |
| CLOUD-1060 | Fixed an issue with KeysManager failing to properly update the exported certificates when a previous export have already been performed. |
| CLOUD-1062 | Fixed KeysManager that wasn't removing temporary files created during the export process |
| CLOUD-1071 | Fixed an issue with the discovery of applications DataReaders/DataWriters when another DataReader/DataWriter previously discovered has left the system |
Version 2.1.1
| Type ID | Description |
|---|---|
| CLOUD-1010 | Fixed a random issue with Load Balancing in LAN-2-LAN deployments which made the data to not be routed |
| CLOUD-998 | Fixed an issue with Load Balancing in case of hierarchical deployment with more than 2 levels. |
| CLOUD-994 | Fixed an issue with Fault Tolerance causing the following warning log: "Unexpected Exception treating SEDP for Writer [...]: java.lang.NullPointerException" |
| CLOUD-1001 | Fixed an issue with Fault Tolerance in indirect-LAN-2-LAN deployments which made the data to not be routed after a switch over. |
| CLOUD-997 | Fixed an issue with Fault Tolerance in Device-2-Device deployments which made the data to not be routed after a switch over. |
Version 2.1.0
| Report ID | Description |
|---|---|
| CLOUD-896 | Added Load Balancing and Fault Tolerance features. See User Guide for more details. |
| CLOUD-924 | Added configuration options: "cloud.blockBuiltinPartition" and "fog.blockBuiltinPartition" to filter out (meaning not routing) all entities using the '_BUILT-IN PARTITION_' partition. And "cloud.blockDurabilityPartition" and "fog.blockDurabilityPartition" to filter out (meaning not routing) all entities using the 'durabilityPartition' partition. Those options are all set to "false" by default. |
| CLOUD-954 | Added the configuration options "cloud.ssl.crl.file" and "fog.ssl.crl.file", and changed the default value of "cloud.ssl.keymanager.algorithm", "fog.ssl.keymanager.algorithm", "cloud.ssl.trustmanager.algorithm" and "fog.ssl.trustmanager.algorithm" from "SunX509" to "PKIX". |
| CLOUD-925 | Updated the Keys Manager tool to generate PEM files for OpenSplice and Vortex Lite (instead of PKCS12 files which are not supported by those products). |
| CLOUD-953 | Updated the Keys Manager tool to generate a single CRL file for all services and devices, in order to simplify the deployment and to fix an issue with restricted devices. |
| CLOUD-986 | Updated the User Guide's "Selective Routing" chapter to clarify the behaviour of Vortex Cloud wrt. selective routing when deployed as an intermediate routing point. |
| CLOUD-853 | Added keys-manager.jar and tool-cmdline.jar which were missing in release 2.0.0. |
| CLOUD-854 | Fix an "INTERNAL ERROR: The local reliability queue for remote Reader is full" message displayed in Cloud/Fog logs in certain circumstances. |
| CLOUD-980 | Fixed java.lang.NullPointerException occurring with Vortex Cloud and Fog when UDP is disabled and a Reader or a Writer is discovered. |
| CLOUD-996 | Fixed a bug that was leading to massive resource consumption when several multicast readers were present in a subsystem. |
| JMOB-1207 | Fixed a possible modification of routed data's timestamp, that could lead to a wrong ordering of samples in case the DDS applications use BY_SOURCE_TIMESTAMP ordering. |
| CLOUD-989 | Fixed interoperability issue occurring with RTI's Connext DDS and causing a java.lang.IllegalArgumentException with message "targetLocator is not UDP". |
| CLOUD-990 | Fixed interoperability issue occurring with OCI's OpenDDS and causing a java.lang.IndexOutOfBoundsException. |
| CLOUD-856 | Added in User Guide the description of SSL configuration properties for Cloud and Fog (in release 2.0.0 those properties existed but were not documented). |
| CLOUD-842 | Fix 1st page of User and Installation Guides PDF documents. |
Version 2.0.0
| Report ID | Description |
|---|---|
| CLOUD-496 | Major change of design wrt. v1.x.y: the Discovery and Routing Services have been replaced by a single Cloud service (Fog service remains as a single application). This results to a simplification of Vortex Cloud/Fog deployment and configuration, as well as improved stability and better performances. Please see User Guide for more details. WARNING: THE SERVICES FROM v2.x.y ARE NOT INTEROPERABLE WITH THE SERVICES FROM v1.x.y (i.e. you should not mix v1 and v2 services in a system). |
| CLOUD-551 | DDS applications can now connect to Vortex Fog via TCP regardless their location (inside the LAN or outside the LAN). |
| CLOUD-516 | Configuring Boundary Security, DDS applications using TCP (typically devices) can now be restricted to connect only to a specific Vortex Fog service or only to Vortex Cloud. |
| CLOUD-790 | Vortex Cloud and Fog now support Java 7 and 8. They are tested with Oracle Java 8. Note that Java 6 is no longer supported. |
| CLOUD-828 | Vortex Cloud and Fog are now based on Vortex Café 2.3.0. They benefit some of its fixes and improvements (see Café's changes). |
| CLOUD-753 | Improve treatment of error cases in Keymanager tool. |
Version 1.3.2
| Report ID | Description |
|---|---|
| CLOUD-671 | Optimization of the routing algorithm, improving the Routing Service performances for both latency and throughput. |
| CLOUD-666 | Vortex Cloud and Fog are now based on Vortex Café 2.2.2. They benefit some of its fixes and improvements (see Café's changes). |
| CLOUD-673 | Fix malformed Heartbeat packets sent to other Vortex products. |
| CLOUD-709 | Fix route termination to properly propagate remote entites deletion to user applications. |
Version 1.3.1
| Report ID | Description |
|---|---|
| CLOUD-475 | Add the possibility in Keys Manager tool to export public/private keys and certificates for devices in PKCS#12 format. Such format is used by OpenSplice and Lite. |
| CLOUD-596 | Add the possibility in Keys Manager tool to revoke certificates and to export a CRL file. |
| CLOUD-580 | Add the "services.tcp.port" configuration property to the command line tool. |
| CLOUD-549 | Add the "fog.faultdetector.td", "fog.faultdetector.tmr", "fog.faultdetector.tm" and "fog.faultdetector.fdf" configuration properties to configure the group management algorithm in Vortex Fog. |
| CLOUD-491 | Setting the "fog.cluster.id" configuration property for Vortex Fog is no longer mandatory. If not set, a unique CLUSTER ID will be generated at start-up. |
| CLOUD-490 | Change both "cloud.discovery.blockBuiltinPartition" and "cloud.discovery.blockDurabilityPartition" configuration properties to be "false" by default. This means the OpenSplice builtin topics and durability topics are now by default routed by Vortex Cloud and Fog. |
| CLOUD-554 | Vortex Cloud and Fog are now based on Vortex Café 2.2.1. They benefit some of its fixes and improvements (see Café's changes). |
Version 1.3.0
| Report ID | Description |
|---|---|
| CLOUD-382 | Add Vortex Fog. See the Vortex Cloud and Fog User Guide for more details. |
| CLOUD-410 | Add Boundary Security. See the Vortex Cloud and Fog User Guide for more details. |
| CLOUD-450 | Change the names of configuration properties for Selective Routing. "cloud.discovery.services.blacklist" is renamed as "cloud.discovery.blacklist.file". "cloud.discovery.services.whitelist" is renamed as "cloud.discovery.whitelist.file". Also change the default value of both to be an empty string (i.e. no file configured). |
| CLOUD-420 | Update the Command Line Tool to support Vortex Fog. Some configuration properties have changed for more consistency: "cloud.tools.domainid" is renamed as "services.domainid". "services.transport" is a new property to be used in place of "ddsi.network.transport". "services.tcp.peers" is a new property to be used in place of "ddsi.discovery.tcp.peers". |
| CLOUD-446 | Vortex Cloud and Fog are now based on Vortex Café 2.2.0. They benefit some of its fixes and improvements (see Café's changes). |
Version 1.2.0
| Report ID | Description |
|---|---|
| CLOUD-288 | Add Selective Routing feature. Now the Discovery Service can be configured with a white-list and/or a black-list of "partition.topic". This allows user specify which partition and/or topic must be routed or not by the Vortex Cloud. |
| CLOUD-305 | Add configuration options on the Discovery Service to not route entities using the OpenSplice's "_BUILT-IN PARTITION_" (cloud.discovery.blockBuiltinPartition=true by default) and to not route entities using the "durabilityPartition" (cloud.discovery.blockDurabilityPartition=true by default). |
| CLOUD-329 | Add the new "cloud.discovery.cluster.id" property for Discovery Service and the new "cloud.routing.cluster.id" property for Routing Service in replacement of respectively "cloud.discovery.lanid" and "cloud.routing.lanid" properties which are now deprecated (but still accepted). The reason of this change is that those properties can also be used for non-LAN sub-systems (e.g. for geographical separation of systems). |
| CLOUD-319 | Add an etc/ directory in Vortex Cloud installation directory. User can copy its license file within. |
| CLOUD-388 | Vortex Cloud is now based on Vortex Café 2.1.1. It benefits some of its fixes and improvements (see Café's changes). |
| CLOUD-363 | Change user guide document to be available in both HTML and PDF formats. Remove installation guide, as now part of the Vortex installer. |
| CLOUD-256 | Update the Routing Service to avoid useless emission of duplicate messages. |
| CLOUD-312 | Fix randomly non-working routes (routes created but data doesn't flow). |
| CLOUD-315 | Fix randomly non-working routes (routes created but data doesn't flow). |
| CLOUD-402 | Fix randomly non-working routes (routes created but data doesn't flow). |
| CLOUD-392 | Fix non-established routes when the Discovery Service needs to create several routes at the same time. |
| CLOUD-365 | Fix detection of route completion: the Discovery Service didn't detect that a route creation was completed by the Routing Services, and didn't advertise the use applications. Consequently the route seemed created, but the data didn't flow. |
| CLOUD-324 | Fix issue with Indirect LAN to LAN scenario: sometimes the routes were not created by the meta-Routing Service, leading the Discovery Services to not discover the Routing Services and to log the message: "ERROR : no available routing service". |
| CLOUD-366 | Fix creation of wrong routes when a user application has several DataReaders or DataWriters on the same topic. |
| CLOUD-381 | Fix "java.lang.NullPointerException" messages when starting a Discovery Service when other Discovery Services are already running in the system. |
| CLOUD-303 | Fix warning message: "WARN [DataReaderListenerThread] cloud.ds - Timeout writing data to null" |
| OSPL-5470 | Fix warning displayed by Discovery and Routing Services: "Java HotSpot(TM) Server VM warning: You have loaded library /tmp/librlm913-5386386880551815362.so which might have disabled stack guard". |
| CLOUD-337 | Fix errors in examples of configuration files: ddsi.discovery.tcp.advertisedLocators was used instead of ddsi.discovery.externalNetworkAddresses - cloud.routing.services.tcp.peers was set to an IP address without port - 08-lan-to-lan-plus-tcp-devices/routing_service_2.properties file contained a wrong IP address for cloud.routing.services.tcp.peers. |
| CLOUD-387 | Fix missing configuration in property in documentation: in chapter "Device to Device & Device to Cloud (private cloud: with multicast)" the Routing Service miss the "cloud.routing.user.udp=true" property. |
Version 1.1.0
| Report ID | Description |
|---|---|
| CLOUD-79 | Add license checking to Discovery Service and Routing Service. |
| CLOUD-313 | Update the LICENSE terms (see LICENSE.html). |
| CLOUD-299 | Vortex Cloud is now based on Vortex Café 2.1.0. It benefits some of its fixes and improvements (see Café's changes). |
| CLOUD-273 | Make Discovery Service to not listen the data exchanges on UDP multicast, thus lowering it's CPU usage. |
| CLOUD-266 | Fix issue making Discovery Service to ignore DDS applications started befor him. |
| CLOUD-242 | Fix interoperability issue with RTI. |
| CLOUD-293 | Fix false detections of Routing Service failure in case of high traffic. |
| CLOUD-296 | Fix "java.util.ConcurrentModificationException" occuring sometime in the Discovery Service. |
| CLOUD-300 | Fix "java.util.ConcurrentModificationException" occuring sometime in the Routing Service. |
Version 1.0.1
| Report ID | Description |
|---|---|
| CLOUD-282 | Vortex Cloud is now based on Vortex Café 2.0.1. It benefits some of its fixes and improvements (see Café's changes). |
| CLOUD-247 | In case Routing Services are not ready when Discovery Service tries to establish a route, the Discovery Service will try again when it detects Routing Services are ready. |
| CLOUD-59 | User Guide improvements. |
| CLOUD-269 | Fix a random issue provoking a newly created route to not work properly (no data routed at all). |
| CLOUD-278 | Fix Routing Service to not drop messages with an INFO_DST which doesn't correspond to itself. |
| CLOUD-264 | Fix java.lang.NullPointerException in tool-cmdline when listing the routes. |
