http-remoting-connector missing error

[narkhed...@gmail.com]

Hi Team,

After migrating from Wildfly 18.0.1 to Wildfly21.0.2, we are seeing below error during startup, even though http-remoting-connector is configured as shown below. Not sure what are we missing in the configuration. 

<subsystem xmlns="urn:jboss:domain:ejb3:8.0">

       <remote cluster="${ejb_cluster}" connectors="http-remoting-connector" thread-pool-name="default"/>

<subsystem xmlns="urn:jboss:domain:remoting:4.0">
                <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>

ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
 ("subsystem" => "ejb3"),
("service" => "remote")
- failure description: {
  "WFLYCTL0412: Required services that are not installed:" => [
        "org.wildfly.clustering.infinispan.cache-container.ejb-cluster;",
       "org.wildfly.clustering.group.ejb-cluster",
       "org.wildfly.clustering.infinispan.default-cache-configuration.ejb-cluster"

    "WFLYCTL0180: Services with missing/unavailable dependencies" => [
         "jboss.ejb.remote.client-mappings.http-remoting-connector is missing [org.wildfly.clustering.group.ejb-cluster]",
        "org.wildfly.clustering.infinispan.cache-configuration.ejb-cluster.http-remoting-connector is missing [org.wildfly.clustering.infinispan.default-cache-configuration.ejb-cluster, org.wildfly.clustering.infinispan.cache-container.ejb-cluster]",
     "org.wildfly.clustering.cache.group.ejb-cluster.http-remoting-connector is missing [org.wildfly.clustering.group.ejb-cluster]",
    "org.wildfly.clustering.infinispan.cache.ejb-cluster.http-remoting-connector is missing [org.wildfly.clustering.infinispan.cache-container.ejb-cluster]"

Thanks & Regards,
Pankaj Narkhede 

[narkhed...@gmail.com]

Can someone please provide inputs on this? not sure what I am missing in the configuration.

I read somewhere that connector-ref=default is deprecated with wildfly21 and onwards. so i tried with https and custom socket binding as well but didn't help. 

[Paul Ferraro]

"WFLYCTL0412: Required services that are not installed:" => [
        "org.wildfly.clustering.infinispan.cache-container.ejb-cluster;",
       "org.wildfly.clustering.group.ejb-cluster",
       "org.wildfly.clustering.infinispan.default-cache-configuration.ejb-cluster"

suggests that your configuration is missing a default-cache within an infinispan cache-container named "ejb-cluster".

[pankaj narkhede]

Hi Paul,

Thanks for the inputs.

suggests that your configuration is missing a default-cache within an infinispan cache-container named "ejb-cluster".  --->  Is this a new requirement/change in wildfly21 because we didn't configure the same in Wildfly18? Why is it complaining about missing the http-remoting-connector then?

Also I tried configuring that but got the same error.  This ejb-cluster is nothing but a variable configured under remote service (remote cluster "${ejb_cluster}") which resolves to respective jvms in a profile. 

Let's say if I have 5 jvms in one profile, do I need to create a cache-container for all ? 

--
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/005ecc86-06c9-41ad-b2d3-c13beedf12ben%40googlegroups.com.

--

[Paul Ferraro]

On Friday, July 14, 2023 at 10:40:36 AM UTC-4 pankaj narkhede wrote:

Hi Paul,

Thanks for the inputs.

suggests that your configuration is missing a default-cache within an infinispan cache-container named "ejb-cluster".  --->  Is this a new requirement/change in wildfly21 because we didn't configure the same in Wildfly18? Why is it complaining about missing the http-remoting-connector then?

I do not recall - as these are both very old releases.  I suspect that this was a "new" requirement to resolves issues with issues with broken EJB client affinity during remote invocations to distributed @Stateful EJBs.

Why chose to migrate to such an old release?

Also I tried configuring that but got the same error.  This ejb-cluster is nothing but a variable configured under remote service (remote cluster "${ejb_cluster}") which resolves to respective jvms in a profile. 

See: https://docs.wildfly.org/21/wildscribe/subsystem/ejb3/service/remote/index.html

The cluster attribute of /subsystem=ejb3/service=remote references the "org.wildfly.clustering.infinispan.cache-container" capability

... which is provided by /subsystem=infinispan/cache-container=*.

 

Let's say if I have 5 jvms in one profile, do I need to create a cache-container for all ? 

If you are doing things correctly, your server configurations (for those servers hosting the same applications) should generally be identical - the differences should be limited to network interfaces and/or port offsets (which should ideally be externalized via properties).

[narkhed...@gmail.com]

Hi Paul,

I was able to resolve this issue by adding individual VM cache-container. looks like I was missing complete domain restart which was causing my changes not reflecting.  

Thanks for your inputs. But still I am not clear how it worked in Wildfly18(without adding individual VMs cache-container) and not in Wildfly21. 

Also I don't see cluster-name attribute option under infinispan/cache-container as mentioned under attributes here.https://docs.wildfly.org/21/wildscribe/subsystem/infinispan/cache-container/index.html

[domain@server1:9999 /] /profile=full-ha/subsystem=infinispan/cache-container=ejb:write-attribute(name=
aliases                     eviction-executor           listener-executor           replication-queue-executor  statistics-enabled
default-cache               jndi-name                   module                      start

Regarding migrating  to old-release is, we want to move step by step to understand changes required in code as well as Wildfly since there are major enhancements in later versions. 

Thanks & Regards,

Pankaj Narkhede 

[Paul Ferraro]

"cluster-name" is a read-only, runtime storage attribute, and thus does not support write-attribute operations.