Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6919638

CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

    XMLWordPrintable

Details

    • gc
    • b01
    • generic, sparc
    • generic, solaris_10

    Backports

      Description

        User reports that when they use NIO, the implementation of the
        gc locker with CMS is causing periods when threads doing get()s and put()s
        on NIO buffers are getting blocked for several seconds at a time.

        They have provided a test case that purportedly reproduces the
        issues that they are having.

        They claim that rewriting their application to avoid the use of NIO
        is avoiding the blockage of threads involved in IO.

        An email trail of the incident and its description and follow-up can
        be found starting at the following URL :-

        http://mail.openjdk.java.net/pipermail/hotspot-gc-use/2010-January/000486.html

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2195168 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2197584 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2197878 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2199779 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2191097 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2193327 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2195158 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2195159 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2195633 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2205254 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

            • P3 - Major loss of function.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8233279 G1: GCLocker GC with +GCLockerInvokesConcurrent spins while cycle in progress

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Enhancement - null JDK-8233280 Remove GCLockerInvokesConcurrent

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Activity

              People

                ysr Y. Ramakrishna
                ysr Y. Ramakrishna
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: