System properties for configuring global client thread pool max size on server side are ignored

In EAP 7.0 you can configure global client thread pool size by system properties. This thread pool is also used by server when Artemis connects to another server. With EAP 7.0, system properties were only possibility to configure global client thread pool size on server.

This changes with EAP7-619. New model attributes are introduced as a part of this RFE.

In current implementation, values specified in model overwrite values set by system properties. In case no value is specified in EAP configuration, default values are used and system properties are overridden.

If customer used system properties to configure client thread pool size in EAP 7.0, this system property based configuration is not taken into account with EAP 7.1.

Shouldn't the system properties have higher priority than model setting? If not, this should be well documented. It would be nice to have a warning message stating that system property configured by you is not taken into account, specify value in model.