[jboss-jira] [JBoss JIRA] (WFLY-11833) Stateful Session Bean affinity URI instead of cluster

[Richard Achmatowicz (Jira)]

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

Richard Achmatowicz edited comment on WFLY-11833 at 4/30/19 10:09 AM:
----------------------------------------------------------------------

It seems that if the bean is created using the Remote home interface (i.e. extends javax.ejb.EJBHome), then the affinity of the associated proxy should be suitable for a remote client. If the bean is created using a Local home interface (i.e. extends javax.ejb.EJBLocalHome), then the associated proxy should be tied to the local environment.

In the case of this issue, the proxy was created with the EJBHome interface and so should be useful in a remote client context, and so probably should have the same affinity as if it were looked up locally from the client (i.e. bean attributes taken into account and end up with a (strong affinity, weak affinity) = (cluster, node session created on)).


was (Author: rachmato):
It seems that if the bean is created using the Remote home interface (i.e. extends javax.ejb.EJBHome), then the affinity of the associated proxy should be suitable for a remote client. If the bean is created using a Local home interface (i.e. extends javax.ejb.EJBLocalHome), then the associated proxy should be tied to the local environment.

> Stateful Session Bean affinity URI instead of cluster
> -----------------------------------------------------
>
>                 Key: WFLY-11833
>                 URL: https://issues.jboss.org/browse/WFLY-11833
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 16.0.0.Final
>         Environment: WildFly cluster having SFSB deployed.
>            Reporter: Joerg Baesner
>            Assignee: Richard Achmatowicz
>            Priority: Major
>              Labels: downstream_dependency
>         Attachments: stateful-timeout.zip
>
>
> Deployed is an application with the following setup:
> * Containing a SFSB (_with passivationCapable="true"_)
> * A SLSB exposing a _remote_ method to a standalone client returning an instance of the SFSB
> Scenario:
> A standalone client is invoking the _remote_ method on the Stateless Session Bean and a new instance of the Stateful Session Bean is returned.
> The issue is that the affinity of the returned Stateful Session Bean is URI instead of Cluster.
> See the attached Gradle reproducer application



--
This message was sent by Atlassian Jira
(v7.12.1#712002)