glassfish
  1. glassfish
  2. GLASSFISH-20366

[Regression] thread is not starting with an interrupted status.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0_b85
    • Fix Version/s: 4.0_b86_RC2
    • Component/s: concurrency
    • Labels:
      None
    • Environment:

      Ubuntu

      Description

      When thread is created by ManagedThreadFactory instance but are started after the ManagedThreadFactory has shut down then thread is not starting with an interrupted status.

        Activity

        Hide
        Alex Pineda added a comment -

        Assigning to Concurrency Dev lead.

        Show
        Alex Pineda added a comment - Assigning to Concurrency Dev lead.
        Hide
        anthony.lai added a comment -
        • What is the impact on the customer of the bug?

        RI behavior is inconsistent with the spec.

        • What is the cost/risk of fixing the bug?

        Low risk. Added a check to interrupt the thread during thread start if the thread is already marked as shutdown.

        • Is there an impact on documentation or message strings?

        No

        • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?

        QL. Concurrency CTS.

        • Which is the targeted build of 4.0 for this fix?

        4.0_b86

        • If this an integration of a new version of a component from another project,
          what are the changes that are being brought in? This might be list of
          Jira issues from that project or a list of revision messages.

        Integration from JSR236 RI project. Only other changes in this new version besides fix for this JIRA issue are only unit tests related.

        Show
        anthony.lai added a comment - What is the impact on the customer of the bug? RI behavior is inconsistent with the spec. What is the cost/risk of fixing the bug? Low risk. Added a check to interrupt the thread during thread start if the thread is already marked as shutdown. Is there an impact on documentation or message strings? No Which tests should QA (re)run to verify the fix did not destabilize GlassFish? QL. Concurrency CTS. Which is the targeted build of 4.0 for this fix? 4.0_b86 If this an integration of a new version of a component from another project, what are the changes that are being brought in? This might be list of Jira issues from that project or a list of revision messages. Integration from JSR236 RI project. Only other changes in this new version besides fix for this JIRA issue are only unit tests related.
        Hide
        anthony.lai added a comment -

        Project: glassfish
        Repository: svn
        Revision: 61627
        Author: anthony.lai
        Date: 2013-04-24 17:04:53 UTC
        Link:

        Log Message:
        ------------
        GLASSFISH-20366 thread from shutdown MTF should start with interrupted state.
        Ran QL and concurrency CTS.

        Revisions:
        ----------
        61627

        Modified Paths:
        ---------------
        trunk/main/appserver/pom.xml
        (pick up fix from JSR236 RI version 1.0-b08)

        Show
        anthony.lai added a comment - Project: glassfish Repository: svn Revision: 61627 Author: anthony.lai Date: 2013-04-24 17:04:53 UTC Link: Log Message: ------------ GLASSFISH-20366 thread from shutdown MTF should start with interrupted state. Ran QL and concurrency CTS. Revisions: ---------- 61627 Modified Paths: --------------- trunk/main/appserver/pom.xml (pick up fix from JSR236 RI version 1.0-b08)

          People

          • Assignee:
            anthony.lai
            Reporter:
            shobhit.singh
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: