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

[Paul Ferraro (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279884#comment-13279884 ] 

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).

> A client is not able to invoke EJB's deployed as "HASingleton deployment"
> -------------------------------------------------------------------------
>
>                 Key: WFLY-6882
>                 URL: https://issues.jboss.org/browse/WFLY-6882
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 10.0.0.Final, 11.0.0.Alpha1
>            Reporter: Wolf-Dieter Fink
>            Assignee: Enrique González Martínez
>
> Given that an application contains a SLSB and is clustered, any EJB client will be updated to have a view off all cluster members and is able to use and failover to any node in the cluster no matter whether it is in the initial list of servers.
> Now if the application is marked as "singleton-deployment" via jboss-all.xml and deployed to all servers only one server in a cluster will pick it and make it active.
> Now the expectation is that a client is routed to that server no matter whether this special server is included in the clients initial connection list.
> The interesting thing is that the client.log show that both servers are connected it the application is NOT marked as singleton
> But only the initial server is connected if the app is marked as singleton!



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)