Uploaded image for project: 'XNIO'
  1. XNIO
  2. XNIO-276

If QueuedNioTcpServer hits the max connection limit it gets stuck in an infinite loop

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.3.4.Final, 3.3.8.Final
    • None
    • None
    • None

    Description

      Hi!

      I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server.
      It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile.

      I'v attached the stack trace but I unfortunately don't see anything according to my knowledge.
      Please help me, I can provide more information if necessary.

      Attachments

        1. stacktrace-brute.txt
          179 kB
        2. stacktrace-forced.txt
          111 kB
        3. Screen Shot 2016-10-13 at 0.39.37.png
          Screen Shot 2016-10-13 at 0.39.37.png
          1.18 MB
        4. pr99-stacktrace.txt
          91 kB
        5. pr99-stacktrace-nonforced.txt
          89 kB
        6. Screen Shot 2016-10-18 at 10.34.23.png
          Screen Shot 2016-10-18 at 10.34.23.png
          835 kB
        7. Screen Shot 2016-10-18 at 10.34.28.png
          Screen Shot 2016-10-18 at 10.34.28.png
          1.15 MB

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7275 Wildfly eats the CPU up to 100% and does not respond

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13272 [GSS](7.1.0) Once hitting the max-connections limit, new connections are not accepted any more and CLOSE_WAIT connections increase gradually

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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-9397 Once hitting the max-connections limit, new connections are not accepted any more and CLOSE_WAIT connections increase gradually

          • 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

              sdouglas1@redhat.com Stuart Douglas
              krisztian.kocsis_jira Krisztian Kocsis (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: