Class VERIFY_SUSPECT2
java.lang.Object
org.jgroups.stack.Protocol
org.jgroups.protocols.VERIFY_SUSPECT2
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionprotected static final recordstatic class -
Field Summary
FieldsModifier and TypeFieldDescriptionprotected intprotected booleanprotected final Set<VERIFY_SUSPECT2.Entry> protected longprotected TimeSchedulerprotected booleanFields 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 voidaddSuspects(Collection<Address> list) Adds suspected members to the suspect list.An event is to be sent down the stack.longprotected Objectvoidinit()Called after a protocol has been created and before the protocol is started.protected booleanremoveSuspect(Address suspect) voidrun()Started when a suspected member is added to suspects.setTimeout(long timeout) voidstart()This method is called on aJChannel.connect(String); starts work.voidstop()Called on aJChannel.disconnect(); stops work (e.g.protected voidvoidAn event was received from the protocol below.A single message was received.voidup(MessageBatch batch) Sends up a multiple messages in aMessageBatch.protected voidverifySuspect(Collection<Address> mbrs) Sends ARE_YOU_DEAD message to suspected_mbr, wait for return or timeoutMethods 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, isErgonomics, level, parse, policies, previewWarning, previewWarning, providedDownServices, providedUpServices, removePolicy, requiredDownServices, requiredUpServices, resetStatistics, resetStats, setAddress, setDownProtocol, setErgonomics, setId, setLevel, setPolicies, setProtocolStack, setSocketFactory, setUpProtocol, setValue, statsEnabled, toString
-
Field Details
-
timeout
protected long timeout -
num_msgs
protected int num_msgs -
use_mcast_rsps
protected boolean use_mcast_rsps -
suspects
-
running
protected boolean running -
timer
-
-
Constructor Details
-
VERIFY_SUSPECT2
public VERIFY_SUSPECT2()
-
-
Method Details
-
getSuspects
-
setTimeout
-
getTimeout
public long getTimeout() -
down
Description copied from class:ProtocolAn event is to be sent down the stack. A protocol may want to examine its type and perform some action on it, depending on the event's type. If the event is a message MSG, then the protocol may need to add a header to it (or do nothing at all) before sending it down the stack usingdown_prot.down(). -
up
Description copied from class:ProtocolAn event was received from the protocol below. Usually the current protocol will want to examine the event type and - depending on its type - perform some computation (e.g. removing headers from a MSG event type, or updating the internal membership list when receiving a VIEW_CHANGE event). Finally, the event is either a) discarded, or b) an event is sent down the stack usingdown_prot.down()or c) the event (or another event) is sent up the stack usingup_prot.up(). -
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. -
run
-
handle
-
verifySuspect
Sends ARE_YOU_DEAD message to suspected_mbr, wait for return or timeout -
addSuspects
Adds suspected members to the suspect list.- Parameters:
list- The list of suspected members
-
removeSuspect
-
unsuspect
-
stopThreadPool
protected void stopThreadPool() -
init
Description copied from class:ProtocolCalled after a protocol has been created and before the protocol is started. Attributes are already set. Other protocols are not yet connected and events cannot yet be sent. -
start
Description copied from class:ProtocolThis method is called on aJChannel.connect(String); starts work. Protocols are connected ready to receive events. Will be called from bottom to top. -
stop
-