[JIRA] Created: (GRIZZLY-1618) SelectorRunner has a bug in thread naming routine.

  • From: "haebin (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [JIRA] Created: (GRIZZLY-1618) SelectorRunner has a bug in thread naming routine.
  • Date: Wed, 11 Dec 2013 13:32:49 +0000 (UTC)
  • Auto-submitted: auto-generated

SelectorRunner has a bug in thread naming routine.
--------------------------------------------------

                 Key: GRIZZLY-1618
                 URL: https://java.net/jira/browse/GRIZZLY-1618
             Project: grizzly
          Issue Type: Bug
            Reporter: haebin


I think it's affecting most of the versions.

If you deploy leader-follower IO strategy, the thread naming routine of 
SelectorRunner runs into a trouble.

2.2.16 (SelectorRunner.java:248)

   currentThread.setName(currentThread.getName() + " SelectorRunner");

Above routine would append " SelectorRunner" endlessly resulting extremely 
long thread name over time.
So, this needs to be fixed asap.

   currentThread.getName().endsWith(" SelectorRunner" ? 
currentThread.getName() : (currentThread.getName() + " SelectorRunner")
 



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[JIRA] Created: (GRIZZLY-1618) SelectorRunner has a bug in thread naming routine.

haebin (JIRA) 12/11/2013

[JIRA] Resolved: (GRIZZLY-1618) SelectorRunner has a bug in thread naming routine.

oleksiys (JIRA) 12/12/2013
Terms of Use; Privacy Policy; Copyright ©2013-2015 (revision 20150226.965aeb8)
 
 
Close
loading
Please Confirm
Close