[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1842) ClusteredIsLocalInterceptor finds unstarted beans

Tue Aug 10 11:10:49 EDT 2010

     [ https://jira.jboss.org/browse/EJBTHREE-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shaun Appleton updated EJBTHREE-1842:
-------------------------------------

    Workaround Description: If this problem occurs when using a HA-Singleton SLSB with a @Clustered annotation a workaround is to remove the @Clustered annotation. Because the @Clustered annotation isn't doing anything useful as the EJB resides only on one node.  (was: If this problem occurs when using a HA-Singleton EJB with a @Clustered annotation a workaround is to remove the @Clustered annotation. Because the @Clustered annotation isn't doing anything useful as, in this case, the EJB resides only on one node.)


> ClusteredIsLocalInterceptor finds unstarted beans
> -------------------------------------------------
>
>                 Key: EJBTHREE-1842
>                 URL: https://jira.jboss.org/browse/EJBTHREE-1842
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: interceptors
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Brian Stansberry
>            Assignee: Paul Ferraro
>
> ClusteredIsLocalInterceptor determines whether a bean is available locally by checking the Ejb3Registry. Problem is beans are registered early in the deployment process, before they are started.
> In the related forum thread pawel.wyrwinski reports how this particularly causes problems when an @Depends("jboss.ha:service=HASingletonDeployer,type=Barrier") annotation is used to make a bean act as an HASingleton. The bean is included in the Ejb3Registry on all nodes but is only started on one.
> A logically obvious solution would be to check whether the target container is started before invoking locally. Unfortunately, AFAICT Container and its subclasses do not expose any method to support such a check.
> Pawel reported this against 4.2.2 so that the "Affects Version" I used, but a quick code check leads me to believe it still exists.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira