[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-216) Different default threadNamePrefix for each ThreadPoolExecutor type

[Manik Surtani (JIRA)]

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

Manik Surtani resolved ISPN-216.
--------------------------------

    Resolution: Done
      Assignee: Manik Surtani  (was: Galder Zamarreno)


> Different default threadNamePrefix for each ThreadPoolExecutor type
> -------------------------------------------------------------------
>
>                 Key: ISPN-216
>                 URL: https://jira.jboss.org/jira/browse/ISPN-216
>             Project: Infinispan
>          Issue Type: Task
>            Reporter: Galder Zamarreno
>            Assignee: Manik Surtani
>             Fix For: 4.0.0.CR1
>
>
> Since there are 4 different usages of ThreadPoolExecutor (ASYNC_NOTIFICATION_EXECUTOR, ASYNC_TRANSPORT_EXECUTOR, EVICTION_SCHEDULED_EXECUTOR, ASYNC_REPLICATION_QUEUE_EXECUTOR) each should have, *by default*, a different thread name prefix. Currently, there's no such thing which means that figuring out what a particular thread belongs to is difficult unless threadNamePrefix are set in each set of properties.

-- 
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