Package org.jgroups.protocols
Class RSVP
- java.lang.Object
-
- org.jgroups.stack.Protocol
-
- org.jgroups.protocols.RSVP
-
- All Implemented Interfaces:
Lifecycle
public class RSVP extends Protocol
Protocol which implements synchronous messages (https://issues.redhat.com/browse/JGRP-1389). A send of a message M with flag RSVP set will block until all non-faulty recipients (one for unicasts, N for multicasts) have acked M, or until a timeout kicks in.- Since:
- 3.1
- Author:
- Bela Ban
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description protected static class
RSVP.Entry
protected class
RSVP.ResendTask
protected static class
RSVP.RsvpHeader
-
Field Summary
Fields Modifier and Type Field Description protected boolean
ack_on_delivery
protected short
current_id
ID to be used to identify messages.protected boolean
handle_unicasts
protected java.util.concurrent.ConcurrentMap<java.lang.Short,RSVP.Entry>
ids
Used to store IDs and their acksprotected java.util.List<Address>
members
protected long
resend_interval
protected java.util.concurrent.Future<?>
resend_task
protected boolean
throw_exception_on_timeout
protected long
timeout
protected TimeScheduler
timer
-
Fields 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 Constructor Description RSVP()
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description boolean
ackOnDelivery()
RSVP
ackOnDelivery(boolean b)
java.lang.Object
down(Event evt)
An event is to be sent down the stack.java.lang.Object
down(Message msg)
A message is sent down the stack.protected <T extends Protocol>
TfindDownProtocol(java.lang.Class<? extends Protocol> cl)
protected short
getNextId()
int
getPendingRsvpRequests()
long
getResendInterval()
long
getTimeout()
protected void
handleResponse(Address member, short id)
boolean
handleUnicasts()
RSVP
handleUnicasts(boolean b)
protected void
handleView(View view)
void
init()
Called after a protocol has been created and before the protocol is started.protected boolean
isResendTaskRunning()
protected void
sendResponse(Address dest, short id)
RSVP
setResendInterval(long i)
RSVP
setTimeout(long t)
void
start()
This method is called on aJChannel.connect(String)
; starts work.protected void
startResendTask()
void
stop()
Called on aJChannel.disconnect()
; stops work (e.g.protected void
stopResendTask()
boolean
throwExceptionOnTimeout()
RSVP
throwExceptionOnTimeout(boolean b)
java.lang.Object
up(Event evt)
An event was received from the protocol below.java.lang.Object
up(Message msg)
A single message was received.void
up(MessageBatch batch)
Sends up a multiple messages in aMessageBatch
.-
Methods inherited from class org.jgroups.stack.Protocol
accept, addPolicy, addr, addr, afterCreationHook, destroy, 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, statsEnabled, toString
-
-
-
-
Field Detail
-
timeout
protected long timeout
-
throw_exception_on_timeout
protected boolean throw_exception_on_timeout
-
ack_on_delivery
protected boolean ack_on_delivery
-
resend_interval
protected long resend_interval
-
current_id
protected short current_id
ID to be used to identify messages. Short.MAX_VALUE (ca 32K plus 32K negative) should be enough, and wrap-around shouldn't be an issue. Using Message.Flag.RSVP should be the exception, not the rule...
-
timer
protected TimeScheduler timer
-
members
protected volatile java.util.List<Address> members
-
ids
protected final java.util.concurrent.ConcurrentMap<java.lang.Short,RSVP.Entry> ids
Used to store IDs and their acks
-
resend_task
protected java.util.concurrent.Future<?> resend_task
-
handle_unicasts
protected boolean handle_unicasts
-
-
Method Detail
-
getPendingRsvpRequests
public int getPendingRsvpRequests()
-
getTimeout
public long getTimeout()
-
setTimeout
public RSVP setTimeout(long t)
-
throwExceptionOnTimeout
public boolean throwExceptionOnTimeout()
-
throwExceptionOnTimeout
public RSVP throwExceptionOnTimeout(boolean b)
-
ackOnDelivery
public boolean ackOnDelivery()
-
ackOnDelivery
public RSVP ackOnDelivery(boolean b)
-
getResendInterval
public long getResendInterval()
-
setResendInterval
public RSVP setResendInterval(long i)
-
handleUnicasts
public boolean handleUnicasts()
-
handleUnicasts
public RSVP handleUnicasts(boolean b)
-
init
public void init() throws java.lang.Exception
Description copied from class:Protocol
Called 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
public void start() throws java.lang.Exception
Description copied from class:Protocol
This method is called on aJChannel.connect(String)
; starts work. Protocols are connected ready to receive events. Will be called from bottom to top.- Specified by:
start
in interfaceLifecycle
- Overrides:
start
in classProtocol
- Throws:
java.lang.Exception
- Thrown if protocol cannot be started successfully. This will cause the ProtocolStack to fail, soJChannel.connect(String)
will throw an exception
-
stop
public void stop()
Description copied from class:Protocol
Called on aJChannel.disconnect()
; stops work (e.g. by closing multicast socket). Will be called from top to bottom.
-
down
public java.lang.Object down(Event evt)
Description copied from class:Protocol
An 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()
.
-
down
public java.lang.Object down(Message msg)
Description copied from class:Protocol
A message is sent down the stack. Protocols may examine the message and do something (e.g. add a header) with it, before passing it down.
-
up
public java.lang.Object up(Event evt)
Description copied from class:Protocol
An 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
public java.lang.Object up(Message msg)
Description copied from class:Protocol
A single message was received. Protocols may examine the message and do something (e.g. add a header) with it before passing it up.
-
up
public void up(MessageBatch batch)
Description copied from class:Protocol
Sends 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 (callingProtocol.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. usingMessageBatch.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.
-
handleView
protected void handleView(View view)
-
handleResponse
protected void handleResponse(Address member, short id)
-
sendResponse
protected void sendResponse(Address dest, short id)
-
getNextId
protected short getNextId()
-
startResendTask
protected void startResendTask()
-
stopResendTask
protected void stopResendTask()
-
isResendTaskRunning
protected boolean isResendTaskRunning()
-
-