Challenge getting logging going via QOS file

It may be that the logs are being buffered and not being flushed to disk.

Are you terminating your program gracefully? Are you calling:

// This should be called on all DomainParticipants
participant->delete_contained_entities();
TheParticipantFactory->delete_participant(participant);

// This should be called after the DomainParticipants have been deleted
TheParticipantFactory->finalize_instance();
 

Gerardo

How does it work with the C++11 API. I tried this settings but they have no effects. But of course I am not using the DomainParticipant Factory. But we use the XML Application Profile to create the Participants as you can see in our config file. Where do I need to add the logging settings?

<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="/opt/rti_connext_dds-5.2.0/resource/schema/rti_dds_profiles.xsd"
version="5.2.0">

<!-- QoS Library containing the QoS profile used in the generated example. A
QoS library is a named set of QoS profiles. -->
<qos_library name="profiles">

<!-- A QoS profile groups a set of related QoS. This QoS profile used to
configure reliable communication between the DataWriter and DataReader
created in the example code. Durability is set to Volatile (default
configuration), so late-joiner subscribers won't get samples sent by
DataWriters in the past. -->
<qos_profile name="default" is_default_qos="true">

<datawriter_qos>
<property>
<value>cd
<!-- The next setting is used to force dynamic memory allocation for
samples with a serialized size of larger than 32K. Without
setting pool_buffer_max_size, all memory would be obtained from a
pre-allocated pool, which would greatly increase the memory usage
in an application that sends large data. -->
<element>
<name>dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size</name>
<value>32768</value>
</element>
</value>
</property>
</datawriter_qos>

<datareader_qos>
<reader_resource_limits>
<!-- Determines whether the DataReader pre-allocates storage for
storing fragmented samples. This setting can be used to limit
up-front memory allocation costs in applications that deal with
large data -->
<dynamically_allocate_fragmented_samples>true</dynamically_allocate_fragmented_samples>
</reader_resource_limits>
<property>
<value>
<!-- The next setting is used to force dynamic memory allocation for
samples with a serialized size of larger than 32K. Without
setting pool_buffer_max_size, all memory would be obtained from
a pre-allocated pool, which would greatly increase the memory
usage in an application that sends large data. -->
<element>
<name>dds.data_reader.history.memory_manager.fast_pool.pool_buffer_max_size</name>
<value>32768</value>
</element>
</value>
</property>
</datareader_qos>

</qos_profile>
</qos_library>

<!-- Domain Library -->
<domain_library name="Domain_Library">
<!-- Set here the domain id used by the dds factory -->
<domain name="${DOMAIN_NAME}" domain_id="${DOMAIN_ID}">
</domain>
</domain_library>

<!-- Participant library -->
<participant_library name="Participant_Library">
<domain_participant name="Participant"
domain_ref="Domain_Library::${DOMAIN_NAME}">
</domain_participant>
</participant_library>
</dds>

Have you maned to get it worked?