Class SIZE
java.lang.Object
org.jgroups.stack.Protocol
org.jgroups.protocols.SIZE
- All Implemented Interfaces:
Lifecycle
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.
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 Summary
FieldsModifier and TypeFieldDescriptionFields inherited from class Protocol
after_creation_hook, down_prot, ergonomics, id, local_addr, log, policies, preview_warning, stack, stats, up_prot -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected static Stringprotected static voidvoidclear()protected static longA message is sent down the stack.downMap()dump()longlongvoidA single message was received.voidup(MessageBatch batch) Sends up a multiple messages in aMessageBatch.upMap()Methods inherited from class Protocol
accept, addPolicy, addr, addr, afterCreationHook, destroy, down, down, enableStats, getAddress, getComponents, getDownProtocol, getDownServices, getId, getIdsAbove, getLevel, getLog, getName, getPolicies, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getUpServices, getValue, init, isErgonomics, level, parse, policies, previewWarning, previewWarning, providedDownServices, providedUpServices, removePolicy, requiredDownServices, requiredUpServices, resetStatistics, setAddress, setDownProtocol, setErgonomics, setId, setLevel, setPolicies, setProtocolStack, setSocketFactory, setUpProtocol, setValue, start, statsEnabled, stop, toString, up
-
Field Details
-
up_map
-
down_map
-
-
Constructor Details
-
SIZE
public SIZE()
-
-
Method Details
-
numDownSamples
public long numDownSamples() -
numUpSamples
public long numUpSamples() -
upMap
-
downMap
-
down
-
up
-
up
Description copied from class:ProtocolSends up a multiple messages in aMessageBatch. 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 - callsProtocol.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. -
clear
public void clear() -
dumpDownSamples
-
dumpUpSamples
-
dump
-
resetStats
public void resetStats()- Overrides:
resetStatsin classProtocol
-
addSample
-
count
-
_dump
-