RTI Connext Java API
Version 6.1.0
|
<<extension>> Configures com.rti.dds.domain.DomainParticipant-independent resources used by RTI Connext. Mainly used to change the maximum number of com.rti.dds.domain.DomainParticipant entities that can be created within a single process (address space). More...
Public Attributes | |
int | max_objects_per_thread |
The maximum number of objects that can be stored per thread for a com.rti.dds.domain.DomainParticipantFactory. More... | |
![]() | |
final QosPolicyId_t | id |
The ID of this QoS policy. More... | |
final String | policy_name |
The name of this QoS policy. More... | |
<<extension>> Configures com.rti.dds.domain.DomainParticipant-independent resources used by RTI Connext. Mainly used to change the maximum number of com.rti.dds.domain.DomainParticipant entities that can be created within a single process (address space).
Within a single process (or address space for some supported real-time operating systems), applications may create and use multiple com.rti.dds.domain.DomainParticipant entities. This QoS policy sets a parameter that places an effective upper bound on the maximum number of com.rti.dds.domain.DomainParticipant entities that can be created in a single process/address space.
int max_objects_per_thread |
The maximum number of objects that can be stored per thread for a com.rti.dds.domain.DomainParticipantFactory.
Before increasing this value to allow you to create more participants, carefully consider the application design that requires you to create so many participants. Remember: a com.rti.dds.domain.DomainParticipant is a heavy-weight object. It spawns several threads and maintains its own discovery database (see DISCOVERY). Creating more participants than RTI Connext strictly requires – one per domain per process/address space – can adversely affect the performance and resource utilization of your application.
[default] 2048; this value allows you to create about 20 or 21 com.rti.dds.domain.DomainParticipant entities.
[range] [1, 1 billion]