New releases of Vortex Link are made available on a regular basis. This page lists all the known issues in the different versions of Vortex Link.
You may also want to read
Please note that Vortex Link was previously two different products – Vortex Cloud and Vortex Fog. These have been merged into a single product with the same feature set.
Known Issues in Vortex Link
If you experience TCP connection failures or if a Link Service is detected as failing by other Link Services despite it seems still up and running:
Please check the MTU configuration of your hosts is coherent with you network.
It may happen that your network has a lower MTU (e.g. 1430 using a VPN) than you hosts (e.g. 1500 usually on ethernet). In such case and if the traffic increases, the TCP protocol will possibly loose packets and try to re-send them grouped in a frame which is bigger than the network MTU. As a consequence the frame will be dropped and the protocol will never be able to re-transmit any packet. No more communication will occur.
You can check the MTU of your host looking at the advanced properties of your network connection (or with ‘ifconfig -a’ command on Unix platforms). And you can check if your host has an appropriate MTU trying to ping a remote host with a packet size equal to your host’s MTU:
- command on Unix platforms: ping -s 1500 remote_host
- command on Windows platforms: ping -l 1500 remote_host
Fault Tolerance with OpenSplice DDS and Vortex Lite:
With current versions of OpenSplice DDS (6.8.0 and below) and Vortex Lite (2.0.7 and below), when a Link service fails, OpenSplice DDS and Vortex Lite may consider the remote DDS applications that were routed by Vortex Link as terminated. After the switch-over of the Link service, OpenSplice DDS and Vortex Lite will re-discover the remote DDS applications. The consequences of this un-discovery and re-discovery are the following:
- Even with RELIABLE QoS their might be some loss of samples during the switch-over.
- Some meta-data will reflect this un-discovery and re-discovery. E.g. :
- instance lifecycles
- subscription matched status and publication matched status
- content of builtin topics