[wildfly-dev] Proposal of an additional JBossThreadPoolExecutor (WFLY-5332)

[David M. Lloyd]

Thanks for the effort to do this.  However it is necessary to point out 
that while you have made a very descriptive flowchart of the logic of 
the thread pool, it is unfortunately not actually a state diagram; it 
does not describe the state of the various data structures, and their 
response to external (possibly asynchronous) stimuli, which is what is 
necessary to ascertain the correctness of a concurrent algorithm such as 
the one at the core of a thread pool.

On 09/24/2015 09:41 AM, Panagiotis Sotiropoulos wrote:
> Hello all,
>
> Because of WFLY-5332, I have modified the JBossThreadPoolExecutor in order to allow the configuration of max-threads and core-threads independently, while preventing the addition of a thread if an idle thread already exists.
> I have attached the state diagrams of the two executors on https://issues.jboss.org/browse/WFLY-5332.
>
> Regards,
> Panagiotis Sotiropoulos
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>

-- 
- DML