-
Bug
-
Resolution: Done
-
Major
-
7.4.0.GA
-
None
-
False
-
False
-
-
-
-
-
-
Undefined
-
After the following commit
WFLYCTL33 is being logged when starting the server with configurations that include the extension, e.g.: standalone.xml.
The issue is not present in 7.4.0.Beta, but can be seen on nightly builds bits:
========================================================================= 11:00:32,876 INFO [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final-redhat-00001 11:00:33,285 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final-redhat-00001 11:00:33,293 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final-redhat-00001 11:00:33,421 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: JBoss EAP 7.4.0.GA (WildFly Core 15.0.0.Final-redhat-20210311v2) starting 11:00:34,252 INFO [org.wildfly.security] (ServerService Thread Pool -- 26) ELY00001: WildFly Elytron version 1.15.1.Final-redhat-00001 11:00:34,627 WARN [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 13) WFLYCTL0033: Extension 'security' is deprecated and may not be supported in future versions 11:00:34,819 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
As can be seen from the log, there's another similar message for a deprecated attribute, but that is treated as an INFO rather than a WARN.
So a question here is - given that we've deprecated security, why should it be still present in current configuration?
- is cloned by
-
-
- Closed
-