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 Naming for easier Thread Dump analysis - CUSTCOM-145 #4405

Merged
merged 2 commits into from
Jan 9, 2020
Merged

Thread Naming for easier Thread Dump analysis - CUSTCOM-145 #4405

merged 2 commits into from
Jan 9, 2020

Conversation

rdebusscher
Copy link

@rdebusscher rdebusscher commented Jan 1, 2020

CUSTCOM-145: Assign meaningful thread names

During Thread dump analysis, it was not always easy to identify what threads are due to their name (Thread-[n] or pool-[x]-thread-[y])

After this update, threads name are mostly set. Some threads are still un named and could be done in

osgi-javaee-base org.glassfish.osgijavaeebase.ExtenderManager.GlassFishServerTracker#addingService
org.glassfish.osgijavaeebase.JavaEEExtender.HybridBundleTrackerCustomizer#addingBundle

and Apache Felix

Description

This is a improvement

Should be easier to identify threads in Thread Dump.

Testing

Testing Performed

Manual testing to identify the list of threads through JConsole.

Test suites executed

  • Quicklook

Testing Environment

Mac OS

@rdebusscher rdebusscher changed the title Thread Naming for easier Thread Dump analysis Thread Naming for easier Thread Dump analysis - CUSTCOM-145 Jan 8, 2020
@rdebusscher rdebusscher requested review from dmatej and jbee January 9, 2020 13:02
@dmatej
Copy link
Contributor

dmatej commented Jan 9, 2020

Jenkins test please

@dmatej dmatej merged commit 6137f3b into payara:master Jan 9, 2020
@rdebusscher rdebusscher deleted the Thread-Naming branch January 20, 2020 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants