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

[Wolf-Dieter Fink (JIRA)]

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

Wolf-Dieter Fink commented on WFLY-6882:
----------------------------------------

[~pferraro] If I deploy an application as a HA Singleton the use-case is that the deployed SLSB/SFSB/Singleton or MDB is only handled by one server in a cluster.
So if I have a cluster of let say 4 nodes one will start the HASingleton. Any Client of this cluster should be able to invoke this application no matter whether this server is in the initial host list or provided by the ejb-client cluster-view update.
This is similar if I deploy a special application only on one node in this cluster.
For MDB it should be no problem as the queue is clustered and anyone in the cluster can send to it but only this MDB(app) is consuming it.

This is a common use-case and should be possible.

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