[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=14007443#comment-14007443 ] 

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

Hi Ingo

It was merged on 29 January (see 
https://github.com/wildfly/wildfly/pull/12941 ) and is in Wildfly 19.

Richard



> 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)