Class PoolingMessageSplitterService

    • Constructor Detail

      • PoolingMessageSplitterService

        public PoolingMessageSplitterService()
    • Method Detail

      • waitQuietly

        protected void waitQuietly​(java.lang.Object monitor)
      • getMaxThreads

        public java.lang.Integer getMaxThreads()
        Set the max number of threads to operate on split messages

        The default is 10 if not explicitly specified

      • setMaxThreads

        public void setMaxThreads​(java.lang.Integer maxThreads)
        Set the max number of threads to operate on split messages

        The default is 10 if not explicitly specified

      • getWarmStart

        public java.lang.Boolean getWarmStart()
        Specify if the underlying object pool should be warmed up on start().

        The default is false if not specified

      • setWarmStart

        public void setWarmStart​(java.lang.Boolean warmStart)
        Specify if the underlying object pool should be warmed up on start().

        The default is false if not specified

      • getWaitWhileBusy

        public java.lang.Boolean getWaitWhileBusy()
        Actively check if the underlying object pool is ready to accept more workers.

        If set to true, then we check that the underlying object pool has enough space for us to submit more jobs. This means that if you have a large number of split messages, then we don't attempt to flood the queue with thousands of messages causing possible issues within constrained environments. It defaults to false if not explicitly specified, and if set to true will have a small negative impact on performance.

      • setWaitWhileBusy

        public void setWaitWhileBusy​(java.lang.Boolean waitWhileBusy)
        Actively check if the underlying object pool is ready to accept more workers.

        If set to true, then we check that the underlying object pool has enough space for us to submit more jobs. This means that if you have a large number of split messages, then we don't attempt to flood the queue with thousands of messages causing possible issues within constrained environments. It defaults to false if not explicitly specified, and if set to true will have a small negative impact on performance.