[
https://issues.jboss.org/browse/WFLY-6882?page=com.atlassian.jira.plugin....
]
Enrique González Martínez commented on WFLY-6882:
-------------------------------------------------
Hi [~pferraro]
I think ejb-client topology and ejb are separate concepts. The topology does not contain
any information about what is deployed (just the info related to connect to that node). I
think is posible to allow the topology to be sent independently if the singleton is
deployed or not and let the ejb-client to query once one node is down. After all setting
up the whole topology statically will throw the same result (most of the endpoint
connections will be useless except one where the singleton is deployed)
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)