[jboss-jira] [JBoss JIRA] Resolved: (JGRP-1136) Streaming state transfer sender pool threads must be named differently

[Galder Zamarreno (JIRA)]

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

Galder Zamarreno resolved JGRP-1136.
------------------------------------

    Resolution: Done


> Streaming state transfer sender pool threads must be named differently
> ----------------------------------------------------------------------
>
>                 Key: JGRP-1136
>                 URL: https://jira.jboss.org/jira/browse/JGRP-1136
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.8
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 2.9
>
>
> The streaming state transfer sender pool should name each of the thread differently! Otherwise, it becomes a nightmare to track individual threads as shown in ISPN-335:
>     private ThreadPoolExecutor setupThreadPool() {
>         ThreadPoolExecutor threadPool = new ThreadPoolExecutor(0, max_pool, pool_thread_keep_alive,
>                 TimeUnit.MILLISECONDS, new SynchronousQueue<Runnable>());
>         ThreadFactory factory = new ThreadFactory() {
>             public Thread newThread(final Runnable command) {
>                 return getThreadFactory().newThread(command, "STREAMING_STATE_TRANSFER sender");
>             }
>         };
>         threadPool.setRejectedExecutionHandler(new ShutdownRejectedExecutionHandler(threadPool
>                 .getRejectedExecutionHandler()));
>         threadPool.setThreadFactory(factory);
>         return threadPool;
>     }
> A counter or similar needs to be added so that each sender thread is named differently.

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