Class BARRIER
- All Implemented Interfaces:
Lifecycle
When an OPEN_BARRIER event is received, we simply open the barrier again and let all messages pass in the up direction. This is done by releasing the WL.
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected final AtomicBooleanprotected Future<?> protected longprotected final Lockprotected longprotected Conditionsignals to waiting threads that the barrier is open againprotected static final Objectprotected TimeSchedulerprotected TPFields inherited from class org.jgroups.stack.Protocol
after_creation_hook, down_prot, ergonomics, id, local_addr, log, policies, stack, stats, up_prot -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected voidvoidClose the barrier.voiddestroy()This method is called on aJChannel.close().An event is to be sent down the stack.protected voidflushQueue(Map<Address, Message> queue) longgetHoles()intlongintvoidinit()Called after a protocol has been created and before the protocol is started.booleanisClosed()booleanvoidprotected Stringprotected voidsetFlushTimeout(long f) setMaxCloseTime(long m) voidstop()Called on aJChannel.disconnect(); stops work (e.g.protected voidAn event was received from the protocol below.A single message was received.voidup(MessageBatch batch) Sends up a multiple messages in aMessageBatch.Methods inherited from class org.jgroups.stack.Protocol
accept, addPolicy, addr, addr, afterCreationHook, down, down, enableStats, getAddress, getComponents, getDownProtocol, getDownServices, getId, getIdsAbove, getLevel, getLog, getName, getPolicies, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getUpServices, getValue, isErgonomics, level, parse, policies, providedDownServices, providedUpServices, removePolicy, requiredDownServices, requiredUpServices, resetStatistics, resetStats, setAddress, setDownProtocol, setErgonomics, setId, setLevel, setPolicies, setProtocolStack, setSocketFactory, setUpProtocol, setValue, start, statsEnabled, toString
-
Field Details
-
max_close_time
protected long max_close_time -
flush_timeout
protected long flush_timeout -
lock
-
barrier_closed
-
no_pending_threads
signals to waiting threads that the barrier is open again -
in_flight_threads
-
barrier_opener_future
-
timer
-
holes
-
mcast_queue
-
ucast_queue
-
transport
-
NULL
-
-
Constructor Details
-
BARRIER
public BARRIER()
-
-
Method Details
-
getMaxCloseTime
public long getMaxCloseTime() -
setMaxCloseTime
-
getFlushTimeout
public long getFlushTimeout() -
setFlushTimeout
-
isClosed
public boolean isClosed() -
getHoles
-
getNumberOfInFlightThreads
public int getNumberOfInFlightThreads() -
getInFlightThreadsCount
public int getInFlightThreadsCount() -
isOpenerScheduled
public boolean isOpenerScheduled() -
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. -
stop
public void stop()Description copied from class:ProtocolCalled on aJChannel.disconnect(); stops work (e.g. by closing multicast socket). Will be called from top to bottom. -
destroy
public void destroy()Description copied from class:ProtocolThis method is called on aJChannel.close(). Does some cleanup; after the call, the VM will terminate -
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
Description copied from class:ProtocolA single message was received. Protocols may examine the message and do something (e.g. add a header) with it before passing it 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. -
unblock
-
closeBarrier
Close the barrier. Temporarily remove all threads which are waiting or blocked, re-insert them after the call- Throws:
TimeoutException
-
openBarrier
public void openBarrier() -
printInFlightThreads
-
flushQueue
-
scheduleBarrierOpener
protected void scheduleBarrierOpener() -
cancelBarrierOpener
protected void cancelBarrierOpener()
-