I wonder if we actually should even be trying to test the number of threads the 
executor has. Isn't that basically the JDK's responsibility? These seem to be 
fairly complicated multithreaded tests for something that isn't even our code. 
Also, do we even have a use case where it makes sense to limit the number of 
threads?



[ Full content available at: https://github.com/apache/geode/pull/2405 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to