public class DELAY extends Protocol
Incoming messages can be delayed independently from outgoing messages (or not delayed at all).
This protocol should be inserted directly above the transport protocol (e.g. UDP).
Modifier and Type | Field and Description |
---|---|
protected boolean |
constant_delay |
protected org.jgroups.protocols.DELAY.DelayedMessageHandler |
delayed_message_handler |
protected DelayQueue<org.jgroups.protocols.DELAY.DelayedMessage> |
delayed_messages |
protected int |
in_delay |
protected int |
in_delay_nanos |
protected int |
out_delay |
protected int |
out_delay_nanos |
after_creation_hook, down_prot, ergonomics, id, log, stack, stats, up_prot
Constructor and Description |
---|
DELAY() |
Modifier and Type | Method and Description |
---|---|
void |
destroy()
This method is called on a
JChannel.close() . |
Object |
down(Message msg)
A message is sent down the stack.
|
int |
getInDelay() |
int |
getInDelayNanos() |
int |
getOutDelay() |
int |
getOutDelayNanos() |
void |
init()
Called after instance has been created (null constructor) and before protocol is started.
|
void |
setInDelay(int in_delay) |
void |
setInDelayNanos(int in_delay_nanos) |
void |
setOutDelay(int out_delay) |
void |
setOutDelayNanos(int out_delay_nanos) |
Object |
up(Message msg)
A single message was received.
|
void |
up(MessageBatch batch)
Sends up a multiple messages in a
MessageBatch . |
accept, afterCreationHook, down, enableStats, getConfigurableObjects, getDownProtocol, getDownServices, getId, getIdsAbove, getLevel, getLog, getName, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getUpServices, getValue, isErgonomics, level, parse, providedDownServices, providedUpServices, requiredDownServices, requiredUpServices, resetStatistics, resetStats, setDownProtocol, setErgonomics, setId, setLevel, setProperties, setProtocolStack, setSocketFactory, setUpProtocol, setValue, start, statsEnabled, stop, up
protected int in_delay
protected int out_delay
protected int in_delay_nanos
protected int out_delay_nanos
protected boolean constant_delay
protected org.jgroups.protocols.DELAY.DelayedMessageHandler delayed_message_handler
protected DelayQueue<org.jgroups.protocols.DELAY.DelayedMessage> delayed_messages
public int getInDelay()
public void setInDelay(int in_delay)
public int getOutDelay()
public void setOutDelay(int out_delay)
public int getInDelayNanos()
public void setInDelayNanos(int in_delay_nanos)
public int getOutDelayNanos()
public void setOutDelayNanos(int out_delay_nanos)
public void init() throws Exception
Protocol
public void destroy()
Protocol
JChannel.close()
.
Does some cleanup; after the call the VM will terminatepublic Object down(Message msg)
Protocol
public Object up(Message msg)
Protocol
public void up(MessageBatch batch)
Protocol
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(org.jgroups.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.getMatchingMessages(short,boolean)
), 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.Copyright © 2018 JBoss, a division of Red Hat. All rights reserved.