The RIC Message Router (RMR) is a thin library which allows applications to send messages to other applications. RMR provides insulation from the actual message transport system (e.g. Nanomsg or NNG), as well as providing endpoint selection based on message type. This page serves as an anchor point for RMR related pages.
WARNING: 15 April 2020
An potential bug has been discovered in the Linux TCP stack and has the potential to affect an xAPP which is trying to connect to another xapp. The bug can be avoided by using ONLY ODD PORT NUMBERS (e.g. 43085). The bug is related to randomly selected port numbers by the connect() system call which seem to always be even values.
Announcements
The following are announcements related to RMR during the past 30 days; newest announcements first.
2020 April 29
Version 4.0.3 was pushed. This change addressed some minor bug complaints highlighted by Sonar. The only potentially serious bug (possible nil pointer use) was in code which parses RMR header version 1 (prior to the introduction of the tracing field), so risk of encountering this is very low.
2020 April 27
Version 4.0.2 was pushed. This fixes a bug in the SI95 transport header interpretation that causes errors when communicating with xAPPs which were linked against RMR 3.6.* and earlier. It is highly recommended that all xAPPs link against 4.0.2 as soon as possible .
...
Version 3.6.2 was pushed. This fixes a bug in the initialisation process when a message is reclaimed from the buffer pool. The flag values are properly initialised. This is considered an important fix and should be picked up by all applications relying on RMR.
Current Version
Release B Bronze Release development (master branch) version tag 4.0.2 3 (27Apr 29 Apr 2020) -- Code is currently frozen; only bug fixes and documentation updates are being applied.
Release A frozen: 1.11.1 (Amber branch) 6 November 2019
...