Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-12395

Upgrade JGroups to 4.1.4.Final

    XMLWordPrintable

Details

    • Component Upgrade
    • Resolution: Done
    • Major
    • 18.0.0.Final
    • None
    • Clustering
    • None

    Description

      Brings in changes for SSL_KEY_EXCHANGE integration.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users WFLY-12164 SSL_KEY_EXCHANGE JGroups protocol should be configured from Elytron capabilities

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Pull Request Sent
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JGRP-2370 SSL_KEY_EXCHANGE creates key_store in init() even if SSLContext is already provided

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JGRP-2371 SSL_KEY_EXCHANGE needs to support distinct client and server SSLContext instances

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JGRP-2373 SSL_KEY_EXCHANGE usage of port_range is off by one; failing with 0 range

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: