Class ClientReliableTopicConfig

  • All Implemented Interfaces:

    public class ClientReliableTopicConfig
    extends java.lang.Object
    implements NamedConfig
    Contains the ReliableTopic configuration for a client.
    See Also:
    • Field Detail


        public static final int DEFAULT_READ_BATCH_SIZE
        The default read batch size.
        See Also:
        Constant Field Values

        public static final TopicOverloadPolicy DEFAULT_TOPIC_OVERLOAD_POLICY
        The default slow consumer policy.
    • Constructor Detail

      • ClientReliableTopicConfig

        public ClientReliableTopicConfig()
      • ClientReliableTopicConfig

        public ClientReliableTopicConfig​(java.lang.String name)
        Creates a new ReliableTopicConfig with default settings.
      • ClientReliableTopicConfig

        public ClientReliableTopicConfig​(ClientReliableTopicConfig reliableTopicConfig)
        Create a clone of given reliable topic
        reliableTopicConfig - topic
    • Method Detail

      • getName

        public java.lang.String getName()
        Gets the name of the reliable topic.
        Specified by:
        getName in interface NamedConfig
        the name of the reliable topic.
      • getTopicOverloadPolicy

        public TopicOverloadPolicy getTopicOverloadPolicy()
        Gets the TopicOverloadPolicy for this reliable topic.
        the TopicOverloadPolicy.
      • setTopicOverloadPolicy

        public ClientReliableTopicConfig setTopicOverloadPolicy​(TopicOverloadPolicy topicOverloadPolicy)
        Sets the TopicOverloadPolicy for this reliable topic. Check the TopicOverloadPolicy for more details about this setting.
        topicOverloadPolicy - the new TopicOverloadPolicy.
        the updated reliable topic config.
        java.lang.IllegalArgumentException - if topicOverloadPolicy is null.
      • getExecutor

        public java.util.concurrent.Executor getExecutor()
        Gets the Executor that is going to process the events. If no Executor is selected, then the ExecutionService.ASYNC_EXECUTOR is used.
        the Executor used to process events.
        See Also:
      • setExecutor

        public ClientReliableTopicConfig setExecutor​(java.util.concurrent.Executor executor)
        Sets the Executor that is going to process the event. In some cases it is desirable to set a specific Executor. For example, you may want to isolate a certain topic from other topics because it contains long running messages or very high priority messages. A single Executor can be shared between multiple Reliable topics, although it could take more time to process a message. If a single Executor is not shared with other reliable topics, then the Executor only needs to have a single thread.
        executor - the Executor. if the executor is null, the ExecutionService.ASYNC_EXECUTOR will be used to process the event.
        the updated config.
      • getReadBatchSize

        public int getReadBatchSize()
        Gets the maximum number of items to read in a batch. Returned value will always be equal or larger than 1.
        the read batch size.
      • setReadBatchSize

        public ClientReliableTopicConfig setReadBatchSize​(int readBatchSize)
        Sets the read batch size. The ReliableTopic tries to read a batch of messages from the ringbuffer. It will get at least one, but if there are more available, then it will try to get more to increase throughput. The minimal read batch size can be influenced using the read batch size. Apart from influencing the number of messages to download, the readBatchSize also determines how many messages will be processed by the thread running the MessageListener before it returns back to the pool to look for other MessageListeners that need to be processed. The problem with returning to the pool and looking for new work is that interacting with an Executor is quite expensive due to contention on the work-queue. The more work that can be done without retuning to the pool, the smaller the overhead. If the readBatchSize is 10 and there are 50 messages available, 10 items are retrieved and processed consecutively before the thread goes back to the pool and helps out with the processing of other messages. If the readBatchSize is 10 and there are 2 items available, 2 items are retrieved and processed consecutively. If the readBatchSize is an issue because a thread will be busy too long with processing a single MessageListener and it can't help out other MessageListeners, increase the size of the threadpool so the other MessageListeners don't need to wait for a thread, but can be processed in parallel.
        readBatchSize - the maximum number of items to read in a batch.
        the updated reliable topic config.
        java.lang.IllegalArgumentException - if readBatchSize is smaller than 1.
      • toString

        public java.lang.String toString()
        toString in class java.lang.Object
      • equals

        public boolean equals​(java.lang.Object o)
        equals in class java.lang.Object
      • hashCode

        public int hashCode()
        hashCode in class java.lang.Object