Jump to content
OpenSplice DDS Forum

Search the Community

Showing results for tags 'keylist instance'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • About OpenSplice DDS
    • News and Events
    • Site Feedback
  • Using OpenSplice DDS
    • General
    • Troubleshooting
  • Understanding OpenSplice DDS
    • OpenSplice DDS Slideshows
    • OpenSplice DDS Movies
  • Community
    • Project: SIMD
    • Project: CamelOS
    • Project: DDS Touchstone
    • Project: RESTful DDS
    • Mac OS X

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Company

Found 1 result

  1. I have created a topic that includes a source and destination ID. The intent is to uniquely identify the source and destination components of each sample. Both the source and destination IDs are defined as keys for the topic. As I understand it, each unique pairing of source and destination ID should define a unique instance. So, if source component 1 publishes a sample with a destination ID of 10 then publishes a second sample with a destination ID of 20, this creates two separate instances within the DDS domain, one with a key of (1,10) and the second with a key of (1,20). At that point, the source component should be able to publish multiple samples to each instance. The problem I'm encountering is that only samples with the lowest-valued destination ID seem to be published. The source can start publishing samples with a key of (1,20) but once it publishes a sample with a key of (1,10) only those samples are published, it can no longer publish samples with a key of (1,20). The DataWriter::write() calls in the source component always return DDS::RETCODE_OK. So, the writes appear to succeed. I've verified this behavior using a subscriber that I implemented and by using the OpenSplice Tuner. Both show the same behavior. I've tried publishing samples to three destination IDs and always only the sample with the lowest key value is published. The order doesn't seem to matter. However, I have noticed that the first sample of each instance is always published. Publish to (1,30) --> Tuner sees the sample Publish to (1,30) --> Tuner sees the sample Publish to (1,30) --> Tuner sees the sample Publish to (1,10) --> Tuner sees the sample Publish to (1,30) --> Tuner DOES NOT see the sample (will no longer see samples with key of (1,30) Publish to (1,10) --> Tuner sees the sample Publish to (1,30) --> Tuner DOES NOT see the sample Publish to (1,10) --> Tuner sees the sample Publish to (1,30) --> Tuner DOES NOT see the sample Publish to (1,20) --> Tuner sees the sample (only first sample of this new instance is visible to the Tuner) Publish to (1,10) --> Tuner sees the sample Publish to (1,30) --> Tuner DOES NOT see the sample Publish to (1,20) --> Tuner DOES NOT see the sample Publish to (1,10) --> Tuner sees the sample Publish to (1,30) --> Tuner DOES NOT see the sample This doesn't make any sense to me. Am I misunderstanding something fundamental about topic keys and instances? Is there some way that topic QoS could be causing this? I'm using the default QoS and OpenSplice 6.5.
×