glassfish
  1. glassfish
  2. GLASSFISH-5243

GlassFish can becomes unresponsible when the requests queue gets full

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 9.1.1
    • Fix Version/s: 9.1.1_dev
    • Component/s: grizzly-kernel
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      5,243
    • Status Whiteboard:
      Hide

      911Approved

      Show
      911Approved

      Description

      GlassFish can becomes unresponsible when it's requests queue reach it's maximum.
      By default, the max pending requests count is 4096. When queue size reach that
      limit, GlassFish starts dropping requests automatically by sending an error page
      to the user using its acceptor thread (SelectorThread).

      If the user isn't reading the response fast enough, there is probability that
      GlassFish can becomes unresponsitive for a short period of time (until the slow
      client read the error page response).

      The workaround is to increase the max-pending-count attribute of
      connection-pool, but that will just delay the problem. The solution is to drop
      the connection when the client isn't reading the response

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            jfarcand
            Reporter:
            jfarcand
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: