Profile Image
Neelakanta

What is the problem in this thread dump?

I have less no of threads in my system but it is still showing problems detected. What are they?


Report URL - https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMjIvMTIvMy90aHJlYWRkdW1wXzIwMjIxMjAzMTEzMzUxNTMzLTAudGR1bXAtLTYtMTgtMjU=

  • problem in thread dump

  • thread from atlassian library

  • memory consuming threads

  • Heap dump

  • diagnose memory problems

Please Sign In or to post your comment or answer

Profile Image

Ram Lakshmanan

Hello Neelakanta!

 Greetings. 

 

 Less number of threads doesn't mean there is no problem in the application. Tool is reporting couple of problems. Let me highlight one of them here.

 

 In your application there is a thread by name 'support-zip'. This thread is originating from the atlassian library. Looks like this atlassian thread is attempting to capture thread dump from your application. It is attempting to capture thread dump across all the 3 dumps file that you uploaded. Frequent thread dump capturing will affect your application performance. You might want to investigate why this atlassian thread is trying to capture thread dumps so frequently. Is there a rationale to it? 

 

 Below is the stack trace of the 'support-zip' atlassian thread:

 

support-zip

PRIORITY : 5
THREAD ID : 0X0000000000000F3D
NATIVE ID : 0
NATIVE ID (DECIMAL) : 0
STATE : RUNNABLE

stackTrace:
java.lang.Thread.State: RUNNABLE
at sun.management.ThreadImpl.dumpThreads0(Native Method)
at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:448)
at com.atlassian.troubleshooting.stp.salext.bundle.threaddump.TDACompatibleThreadDumpGenerator.generateThreadDump(TDACompatibleThreadDumpGenerator.java:71)
at com.atlassian.troubleshooting.stp.salext.bundle.ThreadDumpBundle.generateThreadDump(ThreadDumpBundle.java:98)
at com.atlassian.troubleshooting.stp.salext.bundle.ThreadDumpBundle.getFiles(ThreadDumpBundle.java:66)
at com.atlassian.troubleshooting.stp.zip.ZipFileAppender.getFilesToZip(ZipFileAppender.java:81)
at com.atlassian.troubleshooting.stp.zip.ZipFileAppender.getInnerItems(ZipFileAppender.java:70)
at com.atlassian.troubleshooting.stp.zip.ZipFileAppender.getInnerItems(ZipFileAppender.java:39)
at com.atlassian.troubleshooting.stp.zip.NestedProgressTracker.process(NestedProgressTracker.java:42)
at com.atlassian.troubleshooting.stp.zip.CreateSupportZipTask.addSupportFilesToZip(CreateSupportZipTask.java:134)
at com.atlassian.troubleshooting.stp.zip.CreateSupportZipTask.lambda$null$0(CreateSupportZipTask.java:80)
at com.atlassian.troubleshooting.stp.zip.CreateSupportZipTask$$Lambda$3226/136184480.accept(Unknown Source)
at com.atlassian.troubleshooting.stp.zip.CreateSupportZipTask.writeSupportZipFile(CreateSupportZipTask.java:113)
at com.atlassian.troubleshooting.stp.zip.CreateSupportZipTask.lambda$call$1(CreateSupportZipTask.java:78)
at com.atlassian.troubleshooting.stp.zip.CreateSupportZipTask$$Lambda$3222/1206185495.call(Unknown Source)
at com.atlassian.troubleshooting.stp.zip.CreateSupportZipTask.call(CreateSupportZipTask.java:89)
at com.atlassian.troubleshooting.stp.zip.CreateSupportZipTask.call(CreateSupportZipTask.java:36)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Locked ownable synchronizers:
- java.util.concurrent.ThreadPoolExecutor$Worker@51b99914

Profile Image

Neelakanta

Thanks Ram,

 

It was expected at that time this thread dump is generated.

 

Can you please let me know one more thing how to find memory consuming threads in thread dump?

 

Thanks

Profile Image

Ram Lakshmanan

Hello Neelakanta!

 

 You can use the open source yCrash data script - it will capture the heap dump. Heap dump will indicate largest objects in the application + memory consuming threads. You can use heap dump analysis tools such as yCrash, HeapHero, Eclipse MAT to analyze the heap dump and identify the large object. This video clip may be of use to diagnose memory problems in the application.

 

Got something else on mind? Post Your Question

Not the answer you're looking for? Browse other questions tagged

  • problem in thread dump

  • thread from atlassian library

  • memory consuming threads

  • Heap dump

  • diagnose memory problems

Edit your question

Separate with comma, space or ENTER key. Special characters are not allowed in tag.

Edit your Answer

Edit your Comment