[jboss-jira] [JBoss JIRA] (AS7-3848) @Clustered @Stateless SLSB should send topology information to the client

[Radoslav Husar (JIRA)]

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

Radoslav Husar commented on AS7-3848:
-------------------------------------

Brian, this is a feature request for missing feature from previous AS versions. The filing is based on discussion we had on @Clustered SLSB Jira.

Currently, the EJB client when accessing stateless beans only accesses nodes which are defined in the client's properties files. Thus when new servers are added to the cluster (and the client has not been updated) it will never use the added nodes to request SLSB. The @Clustered annotation has no effect on SLSB ATM. In a sense, when all nodes defined in the client properties are not accessible but the cluster is still up -- the client is not HA.
                
> @Clustered @Stateless SLSB should send topology information to the client
> -------------------------------------------------------------------------
>
>                 Key: AS7-3848
>                 URL: https://issues.jboss.org/browse/AS7-3848
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Clustering, EJB
>    Affects Versions: 7.1.0.Final
>            Reporter: Radoslav Husar
>            Assignee: Paul Ferraro
>              Labels: failover_testing
>             Fix For: 7.1.2.Final
>
>
> Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow deployment.
> The remote ejb client then treats the node as standalone nodes, clustering subsystem is not started. This however means that the topology is static -- compared to AS5 client behavior.
> There are cases where it's useful mainly because the server side is constrained by the pool size of the SLSB (--Jaikiran).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira