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

thread names assigned to all threads created by Hazelcast #9210

Closed
vloo opened this issue Nov 1, 2016 · 1 comment

Comments

Projects
None yet
4 participants
@vloo
Copy link

commented Nov 1, 2016

it would be nice to have names assigned to all threads created by Hazelcast (and not default ones eg: pool-2-thread-1, pool-2-thread-2)
I have found 2 case where Hazelcast creates ThreadPool - but without name pattern
TcpIpConnectionManager:
private final ScheduledExecutorService scheduler = new ScheduledThreadPoolExecutor(4);
and
MetricsRegistryImpl
private final ScheduledExecutorService scheduledExecutorService = new ScheduledThreadPoolExecutor(2);

Have nice day (-:

@vbekiaris vbekiaris added this to the Backlog milestone Nov 1, 2016

@Petikoch

This comment has been minimized.

Copy link

commented Nov 2, 2016

+1

Just wondering why my jvm doesn't shut down and where those pool-x-thread-y threads came from... ;-)

@pveentjer pveentjer modified the milestones: 3.8, Backlog Nov 24, 2016

@pveentjer pveentjer self-assigned this Nov 24, 2016

pveentjer added a commit to pveentjer/hazelcast that referenced this issue Nov 24, 2016

Threads with name 'pool' fixes
MetricsRegistryImpl and TcpIpConnectionManager create a bunch of threads
but the created threads don't have an clear name. This pr fixes that.

Fixes hazelcast#9210
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.