[GLASSFISH-20366] [Regression] thread is not starting with an interrupted status. Created: 22/Apr/13  Updated: 24/Apr/13  Resolved: 24/Apr/13

Status: Resolved
Project: glassfish
Component/s: concurrency
Affects Version/s: 4.0_b85
Fix Version/s: 4.0_b86_RC2

Type: Bug Priority: Major
Reporter: shobhit.singh Assignee: anthony.lai
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu


Tags: 4_0-approved

 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.



 Comments   
Comment by Alex Pineda [ 22/Apr/13 ]

Assigning to Concurrency Dev lead.

Comment by anthony.lai [ 23/Apr/13 ]
  • 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.

Comment by anthony.lai [ 24/Apr/13 ]

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)

Generated at Sun Apr 19 01:51:34 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.