This Jira is reaction to
WFLY-9433 makes validator rules more strict for some attributes in messaging subsystem. Although there is no reason to use these values (which are newly considered as invalid), it was possible to configure them and they worked with Wildfly 11 and previous releases.
As it is proposed in
JBEAP-14110, this change should be done in 2 steps:
- only WARN the user if the parameter is not valid (a negative value other than -1)
- in next release, reject the parameter
I am setting priority as Blocker, because this fix must be included in Wildfly 12 release. It makes no sense to do it later.