a1c3dbe307
* The old implementation would cap the pool size (both corePoolSize and maximumPoolSize) to max-pool-size, which is very confusing becuase maximumPoolSize is only used when the task queue is bounded. * That resulted in configuring core-pool-size-min and core-pool-size-max was not enough, because it could be capped by the default max-pool-size. * The new behavior is simply that maximumPoolSize is adjusted to not be less than corePoolSize, but otherwise the config properties match the underlying ThreadPoolExecutor implementation. * Added a convenience fixed-pool-size property. |
||
|---|---|---|
| .. | ||
| DispatcherDocTest.java | ||
| MyUnboundedJMailbox.java | ||
| MyUnboundedJMessageQueueSemantics.java | ||