-
Bug
-
Resolution: Done
-
Critical
-
8.1.0.Beta
In JBEAP-25040 we deprecated the org.jboss.msc module for use by deployment code, but the HA Singleton feature is based on such use, and that feature is not deprecated. This means users of that feature get deprecation warnings in the log. So we should remove the jboss-api=deprecated setting.
In any Release Note entry for this issue we should note that JBoss MSC includes a number of deprecated APIs and deployments should not use them as they may be removed.
For those trying to understand the comment history on this JIRA, the following is the original issue description, before it was revised on 2025/4/1:
When the ha-singleton-service is deployed it log the warning message
2025-03-20 11:00:12,301 WARN [org.jboss.as.dependency.deprecated] (MSC service thread 1-7) WFLYSRV0221: Deployment "deployment.ha-singleton-service.war" is using a deprecated module ("org.jboss.msc") which may be removed in future versions without notice.
Please update QS to use a new module.
- is caused by
-
JBEAP-25040 Mark the org.jboss.msc module as jboss.api=deprecated
-
- Closed
-
- is incorporated by
-
JBEAP-29892 (8.1.z) Upgrade WildFly Core from 27.0.1.Final-redhat-00006 to 27.1.0.Final-redhat-00001
-
- Verified
-