[jboss-jira] [JBoss JIRA] (JGRP-2016) oob min/max thread doesn't work when oob_thread_pool_queue_enabled = true

[rama rama (JIRA)]

rama rama created JGRP-2016:
-------------------------------

             Summary: oob min/max thread doesn't work when  oob_thread_pool_queue_enabled = true
                 Key: JGRP-2016
                 URL: https://issues.jboss.org/browse/JGRP-2016
             Project: JGroups
          Issue Type: Enhancement
    Affects Versions: 3.6.7
         Environment: Linux 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
            Reporter: rama rama
            Assignee: Bela Ban
            Priority: Critical


hello,

i have noticed that setting
oob_thread_pool_min_threads = 10
oob_thread_pool_max_threads = 100
oob_thread_pool_queue_enabled = true

doesn't create new thread (up to 100) but keep thread number at 10 and queue
items before spawning new threads.

i think that the same behavioud apply to 
thread_pool_queue_enabled = true


What is going to block me, it's that if i set 100 threads, i expect to get higher concurrency 
rather than using queue, and use queue AFTER having finished the max_thread.

in that way the concurrency seem to get limited, am i wrong?

as a workaround i can set 100 as min thread, but seems to waste quite a lot of resource and ctx switch if my working scenario is just to handle spikes of load every time to time (and on the same server i was thinking of running more application that use the same idea, having all of them create 100 threads sound unhealty)

forgive my terrible english, any feedback is appreciated



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)