Publications which are undeliverable because the packet is too large.

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • wd11
    • Affects Version/s: 5
    • Component/s: core
    • None
    • Hide

      Where a Packet is too large to send the Server MUST discard it without sending it and then behave as if it had completed sending that publication.

      In the case of a shared subscription where one or more of the clients cannot receive the message but other clients can receive it. The Sever MUST either discard the message without sending the message to any of the clients, or send the message to one of the clients that can receive it.

      Show
      Where a Packet is too large to send the Server MUST discard it without sending it and then behave as if it had completed sending that publication. In the case of a shared subscription where one or more of the clients cannot receive the message but other clients can receive it. The Sever MUST either discard the message without sending the message to any of the clients, or send the message to one of the clients that can receive it.

      The specification is sparse in its description of how a server should behave when it finds it has a message that cannot be delivered because it is too large.

      One piece of guidance is in section 3.2.2.8 Maximum Packet Size

      Non-Normative comment
      The Server may place the discarded packet on a ‘dead letter queue’ or preform other diagnostic action. Such actions are outside the scope of this specification.

      The situation is clearer for the client because it is able to not send the message in the first place. Other errors, these are either retryable or are detected after the sending of the publication has started.

            Assignee:
            Andrew Banks (Inactive)
            Reporter:
            Andrew Banks (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: