Class UNBATCH

  • All Implemented Interfaces:
    Lifecycle

    public class UNBATCH
    extends Protocol
    Intercepts Protocol.up(MessageBatch) and passes up each message of a message batch as a single message. Mainly to be used in unit tests (https://issues.redhat.com/browse/JGRP-2702).
    Since:
    5.2.18
    Author:
    Bela Ban
    • Field Detail

      • enabled

        protected boolean enabled
    • Constructor Detail

      • UNBATCH

        public UNBATCH()
    • Method Detail

      • enabled

        public boolean enabled()
      • enable

        public UNBATCH enable​(boolean b)
      • up

        public void up​(MessageBatch batch)
        Description copied from class: Protocol
        Sends up a multiple messages in a MessageBatch. The sender of the batch is always the same, and so is the destination (null == multicast messages). Messages in a batch can be OOB messages, regular messages, or mixed messages, although the transport itself will create initial MessageBatches that contain only either OOB or regular messages.

        The default processing below sends messages up the stack individually, based on a matching criteria (calling Protocol.accept(Message)), and - if true - calls Protocol.up(org.jgroups.Event) for that message and removes the message. If the batch is not empty, it is passed up, or else it is dropped.

        Subclasses should check if there are any messages destined for them (e.g. using MessageBatch.iterator(Predicate)), then possibly remove and process them and finally pass the batch up to the next protocol. Protocols can also modify messages in place, e.g. ENCRYPT could decrypt all encrypted messages in the batch, not remove them, and pass the batch up when done.

        Overrides:
        up in class Protocol
        Parameters:
        batch - The message batch