[jboss-jira] [JBoss JIRA] Commented: (JGRP-644) Shared transport: add cluster name to thread name for easier logging

[Bela Ban (JIRA)]

    [ http://jira.jboss.com/jira/browse/JGRP-644?page=comments#action_12413956 ] 
            
Bela Ban commented on JGRP-644:
-------------------------------

This doesn't work for the shared transport where the transport protocol possibly serves more than 1 channel, so we cannot append the cluster name to it.

I recently made some changes to thread naming:

#1 Default thread naming
- Each thread has the local address and cluster name appended, depending on the thread_naming_pattern (default: "cl") in the transport. If ou include the thread name in your log config, this should give you exactly what you want

# Shared transport thread naming
- All threads in the transport (default thread pool, OOB thread pool, timer thread pool) are named with an increasing ID and the local address, e.g. Timer-1,192.168.1.5:4673. We cannot append the cluster name, as a shared transport serves multiple channels (a.k.a clusters)
- All threads *above* the transport (e.g. FD_SOCK server socket handler thread) are named as in the default case, with local address and cluster name appended

> Shared transport: add cluster name to thread name for easier logging
> --------------------------------------------------------------------
>
>                 Key: JGRP-644
>                 URL: http://jira.jboss.com/jira/browse/JGRP-644
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>            Priority: Optional
>             Fix For: 2.7, 2.6.3
>
>


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