Uses of Package
org.jgroups.protocols
Packages that use org.jgroups.protocols
Package
Description
Provides building blocks that are layered on top of channels.
Provides demonstrations of JGroups functionality.
Provides implementations of transport protocols which are
responsible for sending and receiving messages to/from the network.
Support for managing protocol stacks.
Provides useful functionality which cannot be assigned to any particular other package.
-
Classes in org.jgroups.protocols used by org.jgroups.auth
-
Classes in org.jgroups.protocols used by org.jgroups.blocks
-
Classes in org.jgroups.protocols used by org.jgroups.blocks.atomic
-
Classes in org.jgroups.protocols used by org.jgroups.demos
-
Classes in org.jgroups.protocols used by org.jgroups.forkClassDescriptionThe FORK protocol; multiplexes messages to different forks in a stack (https://issues.redhat.com/browse/JGRP-1613).
-
Classes in org.jgroups.protocols used by org.jgroups.protocolsClassDescriptionEncrypts and decrypts communication in JGroups by using a secret key distributed to all cluster members by the key server (coordinator) using asymmetric (public/private key) encryption.
The secret key is identical for all cluster members and is used to encrypt messages when sending and decrypt them when receiving messages.The AUTH protocol adds a layer of authentication to JGroups.AuthHeader is a holder object for the token that is passed from the joiner to the coordinatorAll messages up the stack have to go through a barrier (read lock, RL).Implements storing of messages in a hashmap and sending of single messages and message batches.Shared base class for TCP protocolsBroadcast PING.Pluggable way to collect messages and send them as batchesProtocol which clears a set of flags in the down or up direction for all messagesCompresses the payload of a message.Protocol which is used byCounterServiceto provide a distributed atomic counterDiscards up or down messages based on a percentage; e.g., setting property 'up' to 0.1 causes 10% of all up messages to be discarded.The Discovery protocol retrieves the initial membership (used by GMS and MERGE3) by sending discovery requests.Protocol which drops up or down messages according to user-defined filtersDuplicates outgoing or incoming messages by copying themSuper class of symmetric (SYM_ENCRYPT) and asymmetric (ASYM_ENCRYPT) encryption protocols.Base class for all failure detection protocolsHeader used by various flow control protocolsFailure detection based on simple heartbeat protocol.Failure detection protocol which detects the crash or hanging of entire hosts and suspects all cluster members on those hosts.Command used to check whether a given host is alive, periodically calledFailure detection protocol based on sockets.Task that periodically broadcasts a list of suspected members to the group.Handles a client connection; multiple client can connect at the same timeHandles the server-side of a client-server socket connection.Failure detection protocol based on TCP connections, successor toFD_SOCK.Task which periodically broadcasts a list of suspected members.Simple discovery protocol which uses a file on shared storage such as an SMB share, NFS mount or S3.Simple flow control protocol based on a credit system.The FORK protocol; multiplexes messages to different forks in a stack (https://issues.redhat.com/browse/JGRP-1613).Fragmentation layer.Class represents an entry for a message.Entry for a full message, received fragments are copied into buffer and set in the bitset of expected frags.Base class for all fragmentation protocols.Prints the headers of all sent or received messagesCarries random bits of informationDiscovery protocol using a JDBC connection to a shared database.New version ofJDBC_PING.Base class for protocols implementing key exchange: a secret key to be used for encryption is exchanged between 2 parties (usually the key server and a new cluster member) securely; ie.A local transport is used for sending messages only to single (or all) members of the same host.Intercepts individual up messages and creates batches from them, passing the batches up.Protocol to discover subgroups; e.g., existing due to a network partition (that healed).Uses its own IP multicast socket to send and receive discovery requests/responses.Class which has all the stats about received/sent messages etc.New multicast protocol based on fixed-size xmit windows and message ACKs
Details: https://issues.redhat.com/browse/JGRP-2780The PING protocol retrieves the initial membership by mcasting a discovery request (via the multicast capable transport) to all current cluster membersEncapsulates information about a cluster node, e.g.Used to send discovery requests and responsesA thread safe Rackspace ReST clientMeasures incoming and outgoing rates: messages/sec, bytes/sec.Rate limiter based credits (max_bytes).Deprecated, for removal: This API element is subject to removal in a future version.Functionality replaced by PerDestinationBundler, see https://redhat.atlassian.net/browse/JGRP-3027Base class for reliable multicast protocolsClass which is called by RetransmitTask to resend the last seqno sent (if resend_last_seqno is enabled)Base class for reliable unicast protocolsReverses the next N messages that are received.Protocol which implements synchronous messages (https://issues.redhat.com/browse/JGRP-1389).Header to measure round-trip times (in nanoseconds) for sync RPCs (https://issues.redhat.com/browse/JGRP-2604)Implementation of total order protocol using a sequencer.Loopback transport shared by all channels within the same VM.Reorders messages by buffering them and shuffling the result after TIMEOUT ms.Periodically fetches some attributes and writes them to a file (https://issues.redhat.com/browse/JGRP-2402)Key exchange based on SSL sockets.Helper class that knows how and when to reload the SSLContext.Class which handles a connection to a clientA thread safe Swift clientEncrypts and decrypts communication in JGroups by using a secret key shared by all cluster members.TCP based protocol.Protocol using TCP/IP to send and receive messages.The TCPGOSSIP protocol layer retrieves the initial membership (used by GMS when started by sending event FIND_INITIAL_MBRS down the stack).The TCPPING protocol defines a static cluster membership.Generic transport - specific implementations should extend this class.Base class forTPwhich captures fields and accessors.Generic transport header, used by TP.Replacement for UDP.IP multicast transport based on UDP.InterceptsProtocol.up(MessageBatch)and passes up each message of a message batch as a single message.Unbatches OOB batches when enabled and virtual threads are available.
https://issues.redhat.com/browse/JGRP-2888Reliable unicast protocol using a combination of positive and negative acks.New unicast protocol based on fixed-size xmit windows and message ACKs
Details: https://issues.redhat.com/browse/JGRP-2843Header for subclasses ofReliableUnicast, e.g.Moved out ofUNICAST3into separate class.Catches SUSPECT events traveling up the stack.Double-checks that a suspected member is really dead.
Details: https://issues.redhat.com/browse/JGRP-2558
Design: https://github.com/belaban/JGroups/blob/master/doc/design/VERIFY_SUSPECT2.txtMaintains a version number and adds it to all outbound messages. -
Classes in org.jgroups.protocols used by org.jgroups.protocols.dnsClassDescriptionThe Discovery protocol retrieves the initial membership (used by GMS and MERGE3) by sending discovery requests.
-
Classes in org.jgroups.protocols used by org.jgroups.protocols.relayClassDescriptionReliable unicast protocol using a combination of positive and negative acks.
-
Classes in org.jgroups.protocols used by org.jgroups.stack
-
Classes in org.jgroups.protocols used by org.jgroups.utilClassDescriptionEncapsulates information about a cluster node, e.g.Header to measure round-trip times (in nanoseconds) for sync RPCs (https://issues.redhat.com/browse/JGRP-2604)Generic transport - specific implementations should extend this class.Base class for
TPwhich captures fields and accessors.Generic transport header, used by TP.