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

[Enrique González Martínez (JIRA)]

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

Enrique González Martínez commented on WFLY-6882:
-------------------------------------------------

[~pferraro] I understand the logic of how the system works and thanks for clarify this was by design (something I wasn't aware of). The problem (now I'm making a wild guess) is that the user does not want to lose the advantadge given by configuring just an entry point in the jboss-ejb-client properties and get the full topology (if you add more nodes... you don't need to redeploy anything).

I was trying to create aservice activator (to create a null service with that dependency https://issues.jboss.org/browse/JBEAP-5422?focusedCommentId=13279538&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13279538) for this sort of singleton deployment and it didn't work -maybe I did something wrong but only works in a separte jar (I haven't gone through that part of the code as singleton service has been rewritten).

Not sure if it would be possible to add a mechanism to this singleton deployments where you can set some dependencies that will start even if the ejb is not deployed. That would satisfy the behaviour by design and this special case where the user wants the full topology.

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