Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-3697

Improved lifecycle control of JGroupsChannelLookup

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 6.0.0.CR1
    • Fix Version/s: 6.0.0.Final
    • Component/s: Core
    • Labels:
      None

      Description

      Currently, a JGroupsChannelLookup can indicate whether the JGroupsTransport should connect the provided channel and disconnect/close the provided channel.
      In the case of Wildfly, we'd like to distinguish between disconnect and close. We have a service that provided the channel, but we allow the JGroupsTransport to manage the lifecycle. This leads to conditions where infinispan's cache manager can restart, but the jgroups channel service does not, e.g.
      https://issues.jboss.org/browse/WFLY-2458

      To fix this, I need to introduce hacks into the channel returned by the channel service, such that Channel.close() is a no-op, and introduce a separate method invisible to Infinispan to perform the actual close().

      So what I propose is the following:

      boolean shouldConnect(); // Notice that I renamed this, because there is no such distinction between "start" and "connect".

      boolean shouldDisconnect();

      boolean shouldClose();

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  pferraro Paul Ferraro
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: