Jump to content
OpenSplice DDS Forum
Sign in to follow this  
Emmanuel Prunet

Not being notified of own publications

Recommended Posts


Here is my scenario : I have two publisher and subscriber on a topic for two distinct machines. Both publish and subscribe some content.

Is there a way for my local machine to ignore publication being emitted myself? Or should I create two partitions "Local to Remote" and "Remote to Local" for their DataReader/DataWriter ?


Share this post

Link to post
Share on other sites



If you are sure not to use local to local transport , you could change XML file to set "EnableMulticastLoopback"= false


Or you can use filter to filter topic content , if there is a variable to recognize machine , like topic key .

But this method still cost  DDS transport & discovery resources .


        <Description>Stand-alone 'single-process' deployment and standard DDSI networking.</Description>
        <Service name="ddsi2">
        <Service name="durability">
        <Service name="cmsoap">
    <DDSI2Service name="ddsi2">
            <!-- see the release notes and/or the OpenSplice configurator on DDSI interoperability -->
            <!-- the following one is necessary only for TwinOaks CoreDX DDS compatibility -->
            <!-- <ExplicitlyPublishQosSetToDefault>true</ExplicitlyPublishQosSetToDefault> -->
    <DurabilityService name="durability">
            <WaitForAttachment maxWaitCount="100">
            <NameSpace name="defaultNamespace">
            <Policy alignee="Initial" aligner="true" durability="Durable" nameSpace="defaultNamespace"/>
    <TunerService name="cmsoap">


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this