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. |
||
|---|---|---|
| .. | ||
| index.rst | ||
| issue-tracking.rst | ||
| licenses.rst | ||
| links.rst | ||
| migration-guide-1.3.x-2.0.x.rst | ||
| migration-guide-2.0.x-2.1.x.rst | ||
| migration-guide-2.1.x-2.2.x.rst | ||
| migration-guide-2.2.x-2.3.x.rst | ||
| migration-guide-2.3.x-2.4.x.rst | ||
| migration-guide-2.4.x-2.5.x.rst | ||
| migration-guide-eventsourced-2.3.x.rst | ||
| migration-guide-persistence-experimental-2.3.x-2.4.x.rst | ||
| migration-guides.rst | ||
| sponsors.rst | ||