Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-20199

[GSS](7.3.z) WFLY-13871 - Re-implement correct suspend/resume behaviour for EJB client

    Details

    • Type: Bug
    • Status: Pull Request Sent (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.3.2.GA
    • Fix Version/s: 7.3.5.GA
    • Component/s: EJB
    • Labels:
      None
    • Target Release:
    • Steps to Reproduce:
      Hide
      1. Start a cluster with two nodes where 1 node is suspended.
      2. run a standalone client against the cluster with a configured connection of the node still running (not suspended)

      The client will get a clusterview including the 2nd suspended node and the module including the EJB is available

      Show
      Start a cluster with two nodes where 1 node is suspended. run a standalone client against the cluster with a configured connection of the node still running (not suspended) The client will get a clusterview including the 2nd suspended node and the module including the EJB is available

      Description

      When a server is suspended, in order to avoid receipt of invocations which will never be correctly processed, all connected clients should be notified that all modules on that server are now unavailable; when the server is resumed, all connected clients should be notified that all modules on that server are now again available so that the server may again take part in processing invocations.
      This behavior was present in versions of EAP before EAP 7.1 but was not ported over to the new EJB client server-side classes which were substantially refactored.

      This issue bundles the upstream issue:

      which will re-instante that behavior.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rachmato Richard Achmatowicz
                  Reporter:
                  jbaesner Joerg Baesner
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated: