Package org.jgroups.protocols

Class SIZE

  • All Implemented Interfaces:
    Lifecycle
    public class SIZE
extends Protocol
    Protocol which lists how many messages have been received by size: https://issues.redhat.com/browse/JGRP-2893
    Don't use this layer in a production stack since the costs are high; only use for debugging/diagnosis.
    Author:
    Bela Ban June 13 2001, Bela Ban June 2025

    • Field Detail

      • up_map

        protected final java.util.Map<java.lang.Long,​java.util.concurrent.atomic.LongAdder> up_map

      • down_map

        protected final java.util.Map<java.lang.Long,​java.util.concurrent.atomic.LongAdder> down_map

    • Constructor Detail

      • SIZE

        public SIZE()

    • Method Detail

      • numDownSamples

        public long numDownSamples()

      • numUpSamples

        public long numUpSamples()

      • upMap

        public java.util.Map<java.lang.Long,​java.util.concurrent.atomic.LongAdder> upMap()

      • downMap

        public java.util.Map<java.lang.Long,​java.util.concurrent.atomic.LongAdder> downMap()

      • down

        public java.lang.Object down​(Message msg)
        Description copied from class: Protocol
        A message is sent down the stack. Protocols may examine the message and do something (e.g. add a header) with it, before passing it down.
        Overrides:
        down in class Protocol

      • up

        public java.lang.Object up​(Message msg)
        Description copied from class: Protocol
        A single message was received. Protocols may examine the message and do something (e.g. add a header) with it before passing it up.
        Overrides:
        up in class Protocol

      • 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

      • clear

        public void clear()

      • dumpDownSamples

        public java.lang.String dumpDownSamples()

      • dumpUpSamples

        public java.lang.String dumpUpSamples()

      • dump

        public java.lang.String dump()

      • addSample

        protected static void addSample​(long size,
                                java.util.Map<java.lang.Long,​java.util.concurrent.atomic.LongAdder> map)

      • count

        protected static long count​(java.util.Map<java.lang.Long,​java.util.concurrent.atomic.LongAdder> m)

      • _dump

        protected static java.lang.String _dump​(java.util.Map<java.lang.Long,​java.util.concurrent.atomic.LongAdder> m)