[ https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on WFLY-13871: -------------------------------------------- For each EJBServerChannel which is created on the server side, there is a separate instance of ClusterTopologyListener and ModuleAvailabilityListener created. In the case of ModuleAvailabilityListener, it provides an API with methods such as moduleAvailable(List<EJBModuleIdentifier> modules) and moduleUnavailable(List<EJBModuleIdentifier> modules) which permit notifying the client on the other end of which modules are or are not available. Due to the way individual EJBServerChannels (which unpack and pack messages) are tied into the single AssociationImpl (which processes unpacked invocations and returns unpacked results), these listeners are defined in the EJBServerChannel and instances of them are registered by the AssociationImpl by methods registerClusterTopologyListener and registerModuleAvailabilityListener. This issue can be solved by creating a third listener, SuspendResumeListener and registering it using a method registerSuspendResumeListener in exactly the same way as the others. Then -- This message was sent by Atlassian Jira (v7.13.8#713008)