Not able to start JBoss server.

[Shilpa]

Hi Team,

I upgraded Wildfly 16 to 22 and build got success but when I try to start server then getting the below error:

14:37:03,663 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=ee-security' are not available:
    org.wildfly.weld; There are no known registration points which can provide this capability.

Could anyone please help me on this.

--

Best Regards,

Shilpa

[Darran Lofthouse]

How have you performed the upgrade?  Have you brought in your existing configuration from WildFly 16 or did you modify the default configuration from WildFly 22.

Also do you actually make use of EE security in your deployments?

[Shilpa]

I just downloaded wildfly 22, unzipped to a particular folder and used this folder path in one of my XML configuration file, that's all I did.

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/1f90ceea-6ca6-404e-af59-f9c72ff0da2fn%40googlegroups.com.

[Darran Lofthouse]

Sorry I am not quite following what you mean by "and used this folder path in one of my XML configuration file, that's all I did."

The error you are getting sounds like you have the ee-security subsystem present but the weld extension may not be present, I would expect the capability requirements are already met in the default configuration in the version that we ship.

[Shilpa]

Actually I recently joined this project and related to wildfly configuration we are using one xml file and in that file we are mentioning the wildfly path, other than this nothing doing as a part of the upgrade.

So till now we used Wildfly 16 and now need to upgrade to higher version.

Could you please tell me what I need to do for resolving this issue:

"The error you are getting sounds like you have the ee-security subsystem present but the weld extension may not be present, I would expect the capability requirements are already met in the default configuration in the version that we ship."

To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/d9acab98-c68b-40d8-8de5-cee062c34368n%40googlegroups.com.

--

Best Regards,

Shilpa

[Darran Lofthouse]

I still don't really know what you mean by "wildfly configuration we are using one xml file and in that file we are mentioning the wildfly path" - where does this XML file come from?  Are you talking about the standalone.xml used to configure the server or something else?

Does your deployment make use of EE security?  This would guide the best approach to eliminate the error.  If the deployment does not use EE security then we can likely remote the extension and subsystem from the config, on the other hand if the deployment does use EE security we will need to make sure it's requirements are satisifed.