-
Notifications
You must be signed in to change notification settings - Fork 795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in handling of Data and DataFrag submessages [3091] #142
Comments
Sorry to necro but I wanted to bump this. We're running ROS2 Bouncy, the current release, and we see the same behavior; devices using the Fast-RTPS implementation can fail to receive data when trying to subscribe to topics being emitted by machines using other RMW libs. |
This has been solved by #371, which will be included on release 1.7.1 (#393). Feel free to check it. We will close this issue when it gets merged to master. |
@MiguelCompany Am no longer with ADLINK so don't have access to OpenSplice. However the core DDSI engine has been open sourced as part of the fog05 project (now hosted as an Eclipse IoT project), so you should be able to use this to test. |
@SteveOss I do have tested it myself with the community edition. I was just informing here. |
I am closing this, as it was solved in 1.7.1. Feel free to reopen if still an issue. |
When starting a ROS application I see error messages of the form:
[RTPS_MSG_IN Error] (ID:140012478523136) Bad encapsulation for KeyHash and status parameter list -> Function proc_Submsg_Data
These are being generated as FastRTPS is picking up messages from OpenSplice running in the same domain.
Looking at the source code in src/cpp/rtps/messages/MessageReceiver.cpp
The code for handling the case where the data is just a serialized key looks duff (from line 550):
This code looks lite it's trying to read a parameter list? All there is at this point is a serialized key using
the default sub message endian. There is something similar in the DataFrag handling code, but is commented out. Doesn't look like FastRTPS does anything when Data or DataFrag just contains a key,
but should at least probably decode the sub message correctly and not generate errors.
The text was updated successfully, but these errors were encountered: