We have an issue about sending messages with RMR on some deployments, especially after application stays untouched in long duration (for example 1 week) and reactivated again. We haven’t fully debugged the RMR yet. If you have any idea where should we start and focus on, please let us know, thanks in advance!

Let me summarize;

• App A wants to send RMR message to app B.
• Before sending, App A send itself (to RMR_RTG_SVC) a RMR route update about app B endpoints.
• App A receive RMR message no: 22 that indicates no error in states.

• Actual message is sent by Rmr_send_msg() and it returns RMR_OK.
• But in wireshark, we could not see this message.