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

[Dennis Reed (JIRA)]

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

Dennis Reed commented on WFLY-6882:
-----------------------------------

In EAP 5 and earlier, this was mostly handled by HA-JNDI.  When looking up a singleton in HA-JNDI, you got a non-clustered proxy to whatever node it was deployed on.  If it went down, you looked it up again in HA-JNDI and got a proxy to the new singleton.

Does this still work (new lookup of the EJB)?

> 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.2#72004)