|
RTI Connext Java API
Version 5.0.0
|
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. | |
Public Attributes inherited from QosPolicy | |
| final QosPolicyId_t | id |
| The ID of this QoS policy. | |
| final String | policy_name |
| The name of this QoS policy. | |
Additional Inherited Members | |
Public Member Functions inherited from Struct | |
| abstract boolean | equals (Object obj) |
| abstract int | hashCode () |
| String | toString () |
Protected Member Functions inherited from Struct | |
| Struct () | |
| abstract void | pull_from_nativeI (long native_status) |
| abstract void | push_to_nativeI (long native_status) |
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).
This QoS policy is an extension to the DDS standard.
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] 1024; this value allows you to create about 10 or 11 com.rti.dds.domain.DomainParticipant entities.
[range] [1, 1 billion]