[jboss-jira] [JBoss JIRA] (AS7-4399) Clustering logs have "undefined" thread names.

Wed May 9 23:57:21 EDT 2012

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

Jason Greene updated AS7-4399:
------------------------------

    Fix Version/s: 7.1.3.Final (EAP)
                       (was: 7.1.2.Final (EAP))

    
> Clustering logs have "undefined" thread names.
> ----------------------------------------------
>
>                 Key: AS7-4399
>                 URL: https://issues.jboss.org/browse/AS7-4399
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 7.1.1.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Minor
>             Fix For: 7.1.3.Final (EAP)
>
>
> JGroups typically assigns thread names - this logic seems to be getting bypassed in our custom ThreadFactory.
> e.g.
> 05:30:39,335 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (undefined) ISPN000094: Received new cluster view: [node0002/default|4] [node0002/default, node0003/default, node0004/default]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira