[jboss-jira] [JBoss JIRA] (WFLY-13009) moduleAvailability message is sent before module has started

[Richard Achmatowicz (Jira)]

    [ https://issues.redhat.com/browse/WFLY-13009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957335#comment-13957335 ] 

Richard Achmatowicz commented on WFLY-13009:
--------------------------------------------

Just to note that there can be a significant difference between the time that deploymentAdded is called versus deploymentStarted in the case of @Singleton beans with the @Startup annotation. In this case, the bean with @Startup is asked to perform eager initialization (i.e. the bean is initialized before the deployment starts receiving requests) and there is a mechanism involving StartupCountdown which delays the firing of the deploymentStarted method until the eager initialization completes. This emphasises the fact that the moduleAvailable message really should be sent out on deploymentStarted and not deploymentAvailable.

> moduleAvailability message is sent before module has started
> ------------------------------------------------------------
>
>                 Key: WFLY-13009
>                 URL: https://issues.redhat.com/browse/WFLY-13009
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 19.0.0.Beta1
>            Reporter: Richard Achmatowicz
>            Assignee: Richard Achmatowicz
>            Priority: Major
>
> When EJBs are deployed in a clustered server environment, moduleAvailability messages are sent from the server to all connected EJB client applications in order to inform the client that the module is available on that node. 
> The sending of moduleAvailability messages involves the DeploymentRepository, which records which modules are deployed, and the ModuleAvailabilityListener, which is a DeploymentRepositoryListener which gets called at various stages of module deployment (adding, starting, stopping).
> It looks as though moduleAvailability message are being sent earlier than they should be; in other words, sent when the module is added to the repository and not when the module is later started. This can cause client invocations on the module to return a NoSuchEJBException even after the moduleAvailability message has been sent to the client, causing what is seen in EJBCLIENT-362.
>  



--
This message was sent by Atlassian Jira
(v7.13.8#713008)