Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-3100

Race condition in stop under stress: Context checks block Container stop

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • 5.8.0.GA, 5.8.0.CR1
    • 5.7.4.GA, 6.0.1.GA, 5.7.8.GA
    • tomcat
    • 4
    • False
    • None
    • False
    • Moderate

    Description

      The issue manifests in our StopContextTimeoutTest running under Windows. In this tests we stop a container while it is receiving tens of thousands of parallel requests. So the process of stopping/removing takes a very long time, and sometimes the test framework's start.stop.timeout kicks in and deletes the contexts while the server is stopping.

      Tomcat HostConfig.checkResources sleeps for 500ms in a synchronized method if a resource is not found. This sleep delays the stop of the container and can cause the errors seen in our StopContextTimeoutTest and reported previously in MODCLUSTER-782.

      After some discussion with rhn-engineering-jclere he opened PR-641 that is still not merged either in the tomcat-10 or in the tomcat-9 branches.

      Attachments

        Issue Links

          blocks

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. JWS-2881 Release Notes for 5.8

          • 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.
          • Review
          clones

          Bug - A problem that impairs or prevents the functions of the product. JWS-3092 Race condition in stop under stress: Context checks block Container stop

          • 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.
          • Review
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-819 Race condition in stop under stress: Context checks block Container stop

          • 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 incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JWS-3241 Upgrade mod_cluster to 1.4.5.Final

          • 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

          Activity

            People

              rhn-engineering-jclere Jean-Frederic Clere
              sgala@redhat.com Santiago Gala
              Santiago Gala Santiago Gala
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: