[
https://issues.jboss.org/browse/WFLY-9706?page=com.atlassian.jira.plugin....
]
Brian Stansberry edited comment on WFLY-9706 at 1/18/18 11:00 AM:
------------------------------------------------------------------
If a negative value other than -1 was allowed before but we don't want to allow it any
more, then use a ParameterCorrector to correct it.
I don't know if a WARN is worth it. We need to control our metaspace and the odds that
someone is doing this wrong seems low.
was (Author: brian.stansberry):
If a negative value other than -1 was allowed before but we don't want to allow it any
more, then use a ParameterCorrector to correct it.
Newly added InfiniteOrPositiveValidators to messaging attributes
should just print warning if negative values are not -1
------------------------------------------------------------------------------------------------------------------------
Key: WFLY-9706
URL:
https://issues.jboss.org/browse/WFLY-9706
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 12.0.0.Alpha1
Reporter: Erich Duda
Assignee: Jeff Mesnil
Priority: Blocker
This Jira is reaction to WFLY-9433.
The 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.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)