[jboss-jira] [JBoss JIRA] (WFLY-6882) A client is not able to invoke EJB's deployed as "HASingleton deployment"

[ https://issues.jboss.org/browse/WFLY-6882?page=com.atlassian.jira.plugin.... ] Paul Ferraro edited comment on WFLY-6882 at 8/16/16 1:15 PM: ------------------------------------------------------------- [~elguardian] The truth is that, as currently implemented, the ejb-client topology and ejb deployments are intrinsically related. While it's true that the topology does not contain any information about what is deployed, what is deployed determines the topology. The client mappings registry service (which drives the topology reported to the ejb client) starts in response to an ejb deployment. If an ejb deployment is not started (because it was deployed as a singleton service, and that node is not the primary singleton provider), then the client mappings registry responsible for driving ejb client topology will not start. This was done this way by design, so that the ejb client doesn't attempt to connect to node to which nothing is deployed - however, we can certainly discuss changing this, such that the requisite services start actively (instead of on demand). was (Author: pferraro): [~elguardian] The truth is that the ejb-client topology and ejb deployments are intrinsically related. While it's true that the topology does not contain any information about what is deployed, what is deployed determines the topology. The client mappings registry service (which drives the topology reported to the ejb client) starts in response to an ejb deployment. If an ejb deployment is not started (because it was deployed as a singleton service, and that node is not the primary singleton provider), then the client mappings registry responsible for driving ejb client topology is not started. This was done this way by design, so that the ejb client doesn't attempt to connect to node to which nothing is deployed - however, we can certainly discuss changing this, such that the requisite services start actively (instead of on demand). -- This message was sent by Atlassian JIRA (v6.4.11#64026)