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

ByteBuf leak in Resteasy 3.0.19.SP1, blocker for JDG

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Blocker
    • None
    • None
    • REST
    • None

    Description

      See the linked issues please, JDG 7.1.x is aligned to EAP 7.0.x, but we need this to be fixed as soon as possible due to an upcoming release, so to maintain our alignment, we need this fix included in 7.0.5.GA.

      Is it possible to put this in resteasy 3.0.19.SP2 and include it in EAP 7.0.5.GA?

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1205 RestEasy-Netty4: ByteBuf leak in ResteasyHttpRequestDecoder

          • 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. JDG-708 Netty ByteBuf leak in REST endpoint

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-8599 (7.0.z) Upgrade to RESTEasy from 3.0.19.SP1 to 3.0.19.SP2

          • 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.
          • Verified

          Activity

            People

              psotirop@redhat.com Panagiotis Sotiropoulos
              jsenko@redhat.com Jakub Senko
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: