Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow ThreadNameDeterminer everywhere. #1176

Closed
wants to merge 1 commit into from

Conversation

hgschmie
Copy link

Find a couple of places where threads are created but no
ThreadNameDeterminer can be passed in to control the name of the
threads created. Keep all existing c'tors for backwards compatibility.

Find a couple of places where threads are created but no
ThreadNameDeterminer can be passed in to control the name of the
threads created. Keep all existing c'tors for backwards compatibility.
@ghost
Copy link

ghost commented Mar 19, 2013

Build result for #1176 at 8c96429: Success

@trustin
Copy link
Member

trustin commented Mar 19, 2013

Thanks! Merged via 7013315.

@trustin trustin closed this Mar 19, 2013
@ghost ghost assigned trustin Mar 19, 2013
SergeyMakarenko pushed a commit to facebookarchive/swift that referenced this pull request Sep 28, 2016
- allow setting a name prefix for the threads by calling setName() on the NettyClientConfigBuilder
- make netty actually name the threads in the boss and worker pool
  correctly by passing a ThreadNameDeterminer in.

Setting the name of the timer thread will only work after
- netty/netty#1176 was applied
- the next version of netty gets released with this pull request applied
- the line
   this.hashedWheelTimer = new HashedWheelTimer(renamingDaemonThreadFactory(prefix + "-timer-%s"));
  is replaced by
   this.hashedWheelTimer = new HashedWheelTimer(renamingDaemonThreadFactory(prefix + "-timer-%s"), ThreadNameDeterminer.CURRENT);
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants