Creating writer for ServiceCommandReply

2 posts / 0 new
Log in or register to post comments
Last post
Thu, 01/20/2022 - 15:05
#1
ilya_1725
ilya_1725's picture
Offline
Last seen: 1 year 10 months ago
Joined: 04/20/2020
Posts: 24
Creating writer for ServiceCommandReply

Hi.

I'm trying to create the C++ code to read the RTI::Service::Admin::CommandRequest type (the recorder control message).

But I get the following message during the `narrow` operation

[0x010113EE,0x9FF250E0,0xA7CC36DF:0x80000003{E=DW,T=rti/service/admin/command_reply,C=AdminCommandReply,D=11}|ENABLE] COMMENDLocalWriterRO_init:fragment size not large enough for RTPS overhead
[0x010113EE,0x9FF250E0,0xA7CC36DF:0x80000003{E=DW,T=rti/service/admin/command_reply,C=AdminCommandReply,D=11}|ENABLE] COMMENDLocalWriterRO_init:fragment size not large enough for RTPS overhead
TDataReader::narrow:ERROR: Bad parameter: wrong type reader

The type is not unbounded and I have pool_buffer_max_size set to 4096.

What can be causing this error?

Thank you.

AttachmentSize
File type description XML2.67 KB
Top
Thu, 01/20/2022 - 15:48
garyb
Offline
Last seen: 2 months 3 days ago
Joined: 09/23/2018
Posts: 62

Given the message "fragment size not large enough for RTPS overhead",   you should check to see what your message_size_max  QoS is set to and crank it up. It appears the current setting is smaller than the required minimum for the RTSP header  (~800bytes).   Message_size_max includes the RTPS header size and message.   

We have some handy information in the following community articles.

https://community.rti.com/kb/what-maximum-message-size-supported-rti-connext-4x-and-above

https://community.rti.com/kb/i-am-not-receiving-samples-could-it-be-ip-fragmentation

https://www.rti.com/blog/2017/07/27/who-is-chopping-my-application-data-and-why-should-i-care/

 

Top