Routing Service Memory (6.1.2)

1 post / 0 new
Offline
Last seen: 1 week 4 days ago
Joined: 11/25/2024
Posts: 1
Routing Service Memory (6.1.2)

While debugging some memory issues with out application, we noticed that our RoutingService was reporting an ever-increating value for its periodic "physical memory" metric.
Figured we were configuring something wrong (with history, or lifespan, etc.)

But, if I run up a fairly plain RoutingService via the RTI Launcher (based off of the "DefaultDomainRoute" included in the "RTI_ROUTING_SERVICE.xml" shipped with RTI), I still see this metric increasing.
What's (possibly) even more interesting is that there are no other DDS applications running, other than Admin Console.  So there shouldn't be any actual data being routed through the RoutingService.

Screenshots, and XML provided below:

 

<?xml version="1.0"?>

<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../resource/schema/rti_routing_service.xsd">
     <routing_service name="default">
          <annotation>
               <documentation>Routes all topics from domain 0 to domain 1</documentation>
          </annotation>
          <administration>
               <domain_id>0</domain_id>
          </administration>
          <monitoring>
               <domain_id>0</domain_id>
               <status_publication_period>
                    <sec>5</sec>
                    <nanosec>0</nanosec>
               </status_publication_period>
               <statistics_sampling_period>
                    <sec>1</sec>
                    <nanosec>0</nanosec>
               </statistics_sampling_period>
          </monitoring>
          <domain_route name="DefaultDomainRoute">
               <participant name="domain1">
                    <domain_id>0</domain_id>
               </participant>
               <participant name="domain2">
                    <domain_id>1</domain_id>
               </participant>
               <session name="DefaultSession">
                    <auto_topic_route name="RouteAll">
                         <publish_with_original_info>true</publish_with_original_info>
                         <input participant="domain1">
                              <creation_mode>ON_DOMAIN_AND_ROUTE_MATCH</creation_mode>
                              <allow_topic_name_filter>*</allow_topic_name_filter>
                              <allow_registered_type_name_filter>*</allow_registered_type_name_filter>
                              <deny_topic_name_filter>rti/*</deny_topic_name_filter>
                         </input>
                         <output participant="domain2">
                              <creation_mode>ON_DOMAIN_AND_ROUTE_MATCH</creation_mode>
                              <allow_topic_name_filter>*</allow_topic_name_filter>
                              <allow_registered_type_name_filter>*</allow_registered_type_name_filter>
                              <deny_topic_name_filter>rti/*</deny_topic_name_filter>
                         </output>
                    </auto_topic_route>
               </session>
          </domain_route>
     </routing_service>
</dds>