[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=13454043#comment-13454043 ] 

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

Even if this is working as designed - I would say this is a design problem.
>From a user perspective an EJB which can be called remote and is deployed as a ha-singleton in the cluster the expectation is that the client will automatically updated if the cluster-view changes and is able to invoke the EJB no matter which node is actually elected for the service.
It is not aceptable that the client need to know one of the following
- the (dynamic) address of the node driving the service
- all node addresses of a cluster; as this can change if new nodes are added/removed for performance or maintenance

The point which can be discussed is whether this is a bug or an enhancement.

> 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
(v7.2.3#72005)