This content has been marked as final. Show 1 reply
if you not mark a @Stateless as @Clustered the features are not enabled, that mean
- if there is no other indicator for cluster the cluster modules (JGroups) are not started
- if you access from remote the ejb-client context did not know about the cluster,
i.e. only the server(s) in your client.property (or code) are used, but if clustered the server send a cluster-view back and all other servers in the cluster are used as well
- the client continue with DeploymentNodeSelector instead of using the ClusterNodeSelector
All this features are not available if you use Local interfaces or access the server with the remote-naming (URL remote://) approach.