[infinispan-issues] [JBoss JIRA] Updated: (ISPN-394) Add proper thread naming for server worker threads

[Manik Surtani (JIRA)]

     [ https://jira.jboss.org/jira/browse/ISPN-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani updated ISPN-394:
-------------------------------

    Fix Version/s: 4.1.0.ALPHA3
                       (was: 4.1.0.BETA1)


> Add proper thread naming for server worker threads
> --------------------------------------------------
>
>                 Key: ISPN-394
>                 URL: https://jira.jboss.org/jira/browse/ISPN-394
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Cache Server
>    Affects Versions: 4.1.0.ALPHA2
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.1.0.ALPHA3
>
>
> Add proper worker thread naming capabilities following recommendations from trustin below:
> <galderz> the funny thing that I'm yet to investigate is that we created a ThreadFactory to give a name to the threads but the worker threads used by Netty always look like: "New I/O server worker #"
> <trustin> galderz: manik asked the same question about the thread name - You can change that behavior using ThreadRenamingRunnable.setThreadNameDeterminer()
> <galderz> so, the thread factory in the executor is ignored then?
> <trustin> not ignored but the thread name is set afterwards
> <manik> trustin: yes, we've had this discussion before.  :)
> <galderz> thx trustin, i'll add a jira to fix that
> <galderz> one final thing,
> <galderz> one thing I've spotted is that when a clients disconnect
> <trustin> (overriden that is)

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