Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-1624

AbstractFramedStreamSinkChannel listener check for loop fails with EJB over HTTP

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 2.0.29.Final
    • None
    • Core
    • None
    • Hide

      We need to replace the check by a check that verifies we are not writing data. If that's the case, we close the channel. If not, we just let the listener be called as many times as necessary.

      Show
      We need to replace the check by a check that verifies we are not writing data. If that's the case, we close the channel. If not, we just let the listener be called as many times as necessary.

    Description

      There is a check for a loop in the listener triggered by AbstractFramedStreamSinkChannel.resumeWritesInternal:

                              if (loopCount++ == 100) {
                            //should never happen
                            UndertowLogger.ROOT_LOGGER.listenerNotProgressing();
                            IoUtils.safeClose(AbstractFramedStreamSinkChannel.this);
                            return;
                        }

      This loop count can reach 100 if we are using EJB over HTTP, and close the connection unexpectedly.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18201 [GSS] (7.2.z) WFLY-12822 - UNDERTOW-1623 - Undertow Deadlock

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18265 [GSS](7.3.z) WFLY-12822 - Undertow Deadlock

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. UNDERTOW-689 Potential race when resuming writes in AbstractFramedStreamSinkChannel

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. UNDERTOW-1623 Undertow Deadlock

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          relates to

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4784 Upgrade Undertow to 2.0.29.Final

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

          Activity

            People

              flaviarnn Flavia Rainone
              flaviarnn Flavia Rainone
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: