Hello Community Members,
Getting COMMENDFacade_canSampleBeSent:NOT SUPPORTED | Fragment data not supported by this writer after upgrading to 6.1.2.13.
We are upgrading our RTI Version to 6.1.2.13. Although fragmentation and all related settings are enabled in our QOS File but still seems like fragmentation is not happening, Getting this error in our servicr logs while sending the data and the data is not coming in the RTI Admin console :
COMMENDFacade_canSampleBeSent:NOT SUPPORTED | Fragment data not supported by this writer.
COMMENDAnonWriterService_checkFragmentationSupport:sample cannot be sent
COMMENDAnonWriterService_write:[Local Participant: 101e066 4e6dbce3 bbce8cee | Local Endpoint 100c2] check for local writer fragmentation support failed
PRESPsWriter_writeCommend:!anonw->write
PRESPsWriter_writeInternal:!failed to write sample in Commend
If we are keeping below setting we are getting the above fragmentation error :
<message_size_max>1400</message_size_max>
Observations :
If we are modifying the message_size_max by increasing the size,the data is going out because fragmentation is not triggering and this issue is not coming.
<message_size_max>65507</message_size_max>
We cross checked all the sdds and security files are in right path.
NOTE: we need to use the <message_size_max>1400</message_size_max> and the fragmentation enabled because in all our services it is configured in same way .Increasing the <message_size_max> to 65507 is failing to run other services and failing the receiver to receive the data.
Please reply to this post for any extra info needed for the resolution.
Any supports will be really helpful.Thanks in advance.
So, questions like this should either be sent to your company's internal team that is supporting the DDS integration or you can find the developers at your company who has access to RTI's support portal to submit a question to RTI's support team.
I'm guessing that your problem is that you have to configure Asynchronous Publish Mode for both your application's DataWriters as well as the DDS internal DataWriters used for Discovery.
See this documentation:
https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/users_manual/LargeData_Fragmentation.htm?Highlight=fragment
as well as these
https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/users_manual/LargeData_Fragmentation.htm?Highlight=fragment#Example
https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/users_manual/PUBLISH_MODE_QosPolicy__DDS_Extension_.htm
https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds_professional/users_manual/users_manual/DISCOVERY_CONFIG_Qos.htm
Hello Howard ,
Thanks for your response. we have refered the documents you shared and cross checked the steps meintioned in the document.
All the setting are enables here to trigger fragmentation in our Qos file but still it is not happening.And our only concern is that with higher message_size_max value as 65507 it is working but failing with 1400.
Are we missing any specific QOS setting or any plugin for which fragmentation is not happening. ??
Sorry, I think you will need to contact RTI's support group to dive into this further. To determine if you have set your QOS correctly, we would have to look at the XML QoS profile that you are using to configure your applications. And I would guess that you would not want to post such on this public forum. Please contact RTI's support group (or better yet, contact your internal DDS support team for Axone likely located in Wisconsin and they will be either able to help directly or aid in working with RTI support).