Bug 52955 - Add a ThreadFactory implementation to the ExecutorService used to deploy applications
Summary: Add a ThreadFactory implementation to the ExecutorService used to deploy appl...
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 7
Classification: Unclassified
Component: Catalina (show other bugs)
Version: trunk
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-21 07:55 UTC by Pid
Modified: 2012-06-09 13:35 UTC (History)
0 users


Attachments
ThreadFactory implementation for ContainerBase ExecutorService (2.40 KB, patch)
2012-03-21 07:55 UTC, Pid 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pid 2012-03-21 07:55:31 UTC 
Created attachment 28488 [details]
ThreadFactory implementation for ContainerBase ExecutorService

The current implementation of the ExecutorService (in ContainerBase) uses the default thread factory, producing Threads named "pool-1-thread-1".

Thread properties can be customised using a thread factory, modifying the naming scheme will help users identify container threads.

Patch attached.
Comment 1 Konstantin Kolinko 2012-06-09 13:35:53 UTC 
This feature has been independently implemented by Keiichi Fujino when fixing bug 53342 in r1345026 and will be in 7.0.28.

The thread names are container.getName() + "-startStop-" + number.
E.g. "localhost-startStop-1".