]
Brian Stansberry commented on WFLY-7797:
----------------------------------------
is the
"just dropping" solution. I don't have time to test it now. I wouldn't
be surprised if some subsystem testsuite tweak was required to account for the fact that
the 'none' value is now discarded.
Configuratin for ejb strict-max-pool is confusing regarding
derive-size and max-size
------------------------------------------------------------------------------------
Key: WFLY-7797
URL:
https://issues.jboss.org/browse/WFLY-7797
Project: WildFly
Issue Type: Enhancement
Components: EJB
Reporter: Wolf-Dieter Fink
Assignee: Brian Stansberry
Priority: Minor
Labels: ejb, management
The strict-max pool can be set for automatical configuration with
derive-size (none|from-worker-pools|from-cpu-count) or set the number of pool-entries by
use max-pool-size.
If derive-size is set the use of max-pool-size will throw an error during start that the
use is exclusive.
But as derive-size="none" mean the same as if the attribute is not set it will
be confusing.
- not clear what the pool size is then (I checked it is the default max-pool size =20)
- confusing if it is reset by cli, attr derive-size need to be removed to use max-size
So finally "none" is useless and should be removed.