PID_CONTENT_FILTER_INFO signature limit (32) violates RTPS v2.2 spec 9.6.3.1

[dfjkjf]

Is there an already existing issue for this?

• I have searched the existing issues

Expected behavior

The 32-signature limit in PID_CONTENT_FILTER_INFO submessage violates RTPS v2.2 specification (section 9.6.3.1), which does not define any upper bound for signatures. We recommend extending it to at least 256.

Current behavior

When using content filtering, the PID_CONTENT_FILTER_INFO submessage enforces a maximum of 32 signatures, which conflicts with RTPS v2.2 specification (section 9.6.3.1).

Steps to reproduce

1. Launch 50 instances of clientApp.
2. Observe the number of filterSignatures in the PID_CONTENT_FILTER_INFO field of Data submessages in the network capture.
3. Start one instance of serverApp.

Fast DDS version/commit

3.0.1

Platform/Architecture

Ubuntu Focal 20.04 amd64

Transport layer

UDPv4

Additional context

• RTPS v2.2 spec section 9.6.3.1.
• Related example: [fastdds/examples/cpp/request_reply].

XML configuration file

Relevant log output

2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '1' to client 01.0f.65.91.2a.b5.43.66.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.2a.b5.43.66.00.00.00.00
2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '2' to client 01.0f.65.91.2a.b5.43.66.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.2a.b5.43.66.00.00.00.00
2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '3' to client 01.0f.65.91.2a.b5.43.66.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.2b.b5.17.a0.00.00.00.00
2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '1' to client 01.0f.65.91.2b.b5.17.a0.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.2b.b5.17.a0.00.00.00.00
2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '2' to client 01.0f.65.91.2b.b5.17.a0.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.34.b6.cd.d6.00.00.00.00
2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '4' to client 01.0f.65.91.34.b6.cd.d6.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.2b.b5.17.a0.00.00.00.00
2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '3' to client 01.0f.65.91.2b.b5.17.a0.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.2b.b5.17.a0.00.00.00.00
2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '4' to client 01.0f.65.91.2b.b5.17.a0.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.60.b5.6c.d1.00.00.00.00
2025-07-10T17:25:16.748 [ERROR] [ServerApp] Failed to send reply to request with ID '1' to client 01.0f.65.91.60.b5.6c.d1.00.00.00.00
2025-07-10T17:25:16.748 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.31.b6.cf.db.00.00.00.00
2025-07-10T17:25:16.749 [ERROR] [ServerApp] Failed to send reply to request with ID '1' to client 01.0f.65.91.31.b6.cf.db.00.00.00.00
2025-07-10T17:25:16.749 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.31.b6.cf.db.00.00.00.00
2025-07-10T17:25:16.749 [ERROR] [ServerApp] Failed to send reply to request with ID '2' to client 01.0f.65.91.31.b6.cf.db.00.00.00.00
2025-07-10T17:25:16.749 [DEBUG] [ServerApp] Processing request from client 01.0f.65.91.31.b6.cf.db.00.00.00.00

Network traffic capture

No response

[dfjkjf]

writer_qos.writer_resource_limits().reader_filters_allocation.maximum