Private stream silently drops messages if receiving side is running slowly

Unknown
Unknown
in TREP Infrastructure

On an established private stream, if one side is sending messages faster than the other side is able to process them it appears that this results in messages being silently dropped somewhere on the server side without any indication in the (ADS or ADH) log files. The private stream remains established and in an OK state while this happens with no indication data has been missed.

Is this the expected behaviour? Where along the private stream message pathway are the messages being discarded?

adh-3.2.0.L1-rhel6-x86-rrg

ads-3.0.4.L1-rhel6-x86-rrg

Tagged:

Best Answer

Answers

  • Jirapongse
    Jirapongse

    According to the ETA developer guide, private streams behave in a manner similar to standard streams, with the following exceptions:

    • All data on a private stream flow between the end provider and the end consumer of the stream
    • Intermediate components do not fan out content (i.e., do not distribute it to other consumers)
    • Intermediate components should not cache content
    • In the event of connection or data loss, intermediate components do not recover content. All private stream recovery is the responsibility of the consumer application

    Typically, the messages shouldn't be silently dropped. You can submit this query to TREP support team via Get Support to verify its settings, or log files.

  • Unknown
    Unknown

    Hi, your development centre have confirmed that generic messages can be silently dropped, we have made an enhancement request to improve this situation. Perhaps you could check with them for more details and improve the answer. Thanks.

Categories