Jump to content
OpenSplice DDS Forum

Vivek Pandey

  • Content Count

  • Joined

  • Last visited

About Vivek Pandey

  • Rank

Profile Information

  • Company
    ADLINK Technology
  1. Dear Dalcelay, .NET core isn't officially supported but we already did some tests with it. In our commercial version we can support it if customer requires. With best regards, Vivek Pandey Solutions Architect ADLINK Technologies
  2. Dear Mr. ChatrapatiGV, May I know which version of Opensplice DDS you are using. also let me know which DDS API (C, C++, ISOC++,...) you are using. This information is required to address your queries. With best regards, Vivek
  3. You can go though the below link to understand the firewall and ddsi networking port controlling in dds communication. https://istkb.adlinktech.com/article/ddsi-networking-service-ports/ Thanks
  4. Hi Trs91, Here is the fix for similar problem: Regarding nature of create_topic() API : It creates a reference to a new or existing Topic under the given name, for a specific type, with the desired QosPolicy settings and if applicable, attaches the optionally specified TopicListener to it. You can get details from below link: http://download.ist.adlinktech.com/docs/Vortex/apis/ospl/cs_api/html/a00928.html#a83346dafb28e1fe8f7f3aa5c545fe97f With best regards, Vivek Pandey Solutions Architect Adlink Technology
  5. Dear Luca, The problem is because of network disconnection and re-connection (for a moment) between two nodes. As the result of disconnection between data writer and data reader the instances go to NOT_ALIVE_NO_WRITER/NOT_ALIVE_DISPOSED state. I suppose you are using take call. take may remove the instance from the reader administration when the instance becomes empty. When the network connection is restored then either the durability service will realign the data or writer (in case of transient_local) may resent it's data again. Because the instance was removed as a result of the take, a
  6. DurablePolicies is not required because you are using TRANSIENT_LOCAL_DURABILITY_QOS and ddsi service. If ddsi is used then durability has NOTHING to do with transient-data delivery because ddsi is responsible for the alignment of builtin topics. In fact, you don't need a durability service at all to experience transient-local behavior when ddsi is used. DurablePolicies is only required when you don't run durability service locally , but to request data from a durability service on a remote federation using the client-durability feature. I am not sure about the cause of your segmentation
  • Create New...