<div dir="ltr">Bela, do you really need to rename the thread? You already pass a name argument to the Thread constructor, why not create the thread with the "correct" name directly?<br><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Thu, Oct 17, 2013 at 5:48 PM, Dennis Reed <span dir="ltr"><<a href="mailto:dereed@redhat.com" target="_blank">dereed@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im">On 10/17/2013 05:26 AM, Bela Ban wrote:<br>
> The other thing to look at is the apparent cost of Thread.setName(): if<br>
> we cannot avoid thread many creations, we could experiment with *not*<br>
> naming threads, although this is IMO not a good idea.<br>
<br>
</div>I agree that not naming the threads is a bad idea.<br>
<br>
The thread names are vital for debugging -- both in log messages and in<br>
thread dumps.<br>
Not naming the threads would lose a whole lot of information.<br>
<span class=""><font color="#888888"><br>
-Dennis<br>
</font></span><div class=""><div class="h5">_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div></div>