E- the type of the message
public interface ITopic<E> extends DistributedObject
When a member subscribes for a topic, it is actually registering for messages published by any member in the cluster, including the new members joined after you added the listener.
Messages are ordered, meaning that listeners(subscribers) will process the messages in the order they are actually published. If cluster member M publishes messages m1, m2, m3...mn to a topic T, then Hazelcast makes sure that all of the subscribers of topic T will receive and process m1, m2, m3...mn in order.
Since Hazelcast 3.5 it is possible to have reliable topics. Normally all
topics rely on the shared eventing system and shared threads. With Hazelcast
3.5 it is possible to configure a topic to be reliable and to get its own
Ringbuffer to store events and to get its
own executor to process events. The events in the ringbuffer are replicated,
so they won't get lost when a node goes down.
|Modifier and Type||Method and Description|
Subscribes to this topic.
Returns statistics about this topic, like total number of publishes/receives.
Returns the name of this ITopic instance.
Publishes the message to all subscribers of this topic.
Stops receiving messages for the given message listener.
message- the message to publish to all subscribers of this topic
TopicOverloadException- if the consumer is too slow (only works in combination with reliable topic)
@Nonnull UUID addMessageListener(@Nonnull MessageListener<E> listener)
MessageListener.onMessage(Message)method of the given MessageListener is called. More than one message listener can be added on one instance.
listener- the MessageListener to add
NullPointerException- if listener is
If the given listener already removed, this method does nothing.
registrationId- ID of listener registration
trueif registration is removed,
Copyright © 2020 Hazelcast, Inc.. All rights reserved.