Troubleshooting real production problems

Troubleshooting Real Production Problems
Ram Lakshmanan
Architect: GCeasy.io, fastThread.io, HeapHero.io

https://blog.fastthread.io/2018/12/13/how-to-troubleshoot-cpu-problems/
Troubleshooting CPU spike

Step 1: Confirm
Don‘t trust anyone
‘top’ tool is your good friend

Step 2: Identify Threads
Example:
top -H -p 31294
top –H –p {pid}

Step 3: Capture thread dumps
JDK tool. Now Open source. GUI based
option.
jVisualVMkill -3
Kill -3 <pid>
Useful when only JRE is installed
jstack (since Java 5)
jstack -l <pid> > /tmp/threadDump.txt
Few APM Tools does provide this support
APM ToolsThreadMXBean
Programmatic way to capture thread
dumps
Windows (Ctrl + Break)
https://blog.fastthread.io/2016/06/06/how-to-take-thread-dumps-7-options/
030201
070605
option.
JMC
jcmd <pid> Thread.print >
/tmp/threadDump.txt
Jcmd (since Java 7)
04
08
Helpful during development phase

2019-02-26 17:13:23
Full thread dump Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode):
"Reconnection-1" prio=10 tid=0x00007f0442e10800 nid=0x112a waiting on condition [0x00007f042f719000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x007b3953a98> (a java.util.concurrent.locks.AbstractQueuedSynchr)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.lang.Thread.run(Thread.java:722)
:
:
1
2
3
1 Timestamp at which thread dump was triggered
2 JVM Version info
3 Thread Details - <<details in following slides>>
Anatomy of thread dump
"InvoiceThread-A996" prio=10 tid=0x00002b7cfc6fb000 nid=0x4479 runnable [0x00002b7d17ab8000]
java.lang.Thread.State: RUNNABLE
at com.buggycompany.rt.util.ItinerarySegmentProcessor.setConnectingFlight(ItinerarySegmentProcessor.java:380)
at com.buggycompany.rt.util.ItinerarySegmentProcessor.processTripType0(ItinerarySegmentProcessor.java:366)
at com.buggycompany.rt.util.ItinerarySegmentProcessor.processItineraryByTripType(ItinerarySegmentProcessor.java:254)
at com.buggycompany.rt.util.ItinerarySegmentProcessor.templateMethod(ItinerarySegmentProcessor.java:399)
at com.buggycompany.qc.gds.InvoiceGeneratedFacade.readTicketImage(InvoiceGeneratedFacade.java:252)
at com.buggycompany.qc.gds.InvoiceGeneratedFacade.doOrchestrate(InvoiceGeneratedFacade.java:151)
at com.buggycompany.framework.gdstask.BaseGDSFacade.orchestrate(BaseGDSFacade.java:32)
at com.buggycompany.framework.gdstask.BaseGDSFacade.doWork(BaseGDSFacade.java:22)
at com.buggycompany.framework.concurrent.BuggycompanyCallable.call(buggycompanyCallable.java:80)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

"InvoiceThread-A996" prio=10 tid=0x00002b7cfc6fb000 nid=0x4479 runnable [0x00002b7d17ab8000]
java.lang.Thread.State: RUNNABLE
at com.buggycompany.rt.util.ItinerarySegmentProcessor.setConnectingFlight(ItinerarySegmentProcessor.java:380)
at com.buggycompany.rt.util.ItinerarySegmentProcessor.processTripType0(ItinerarySegmentProcessor.java:366)
at com.buggycompany.rt.util.ItinerarySegmentProcessor.processItineraryByTripType(ItinerarySegmentProcessor.java:254)
at com.buggycompany.rt.util.ItinerarySegmentProcessor.templateMethod(ItinerarySegmentProcessor.java:399)
at com.buggycompany.qc.gds.InvoiceGeneratedFacade.readTicketImage(InvoiceGeneratedFacade.java:252)
at com.buggycompany.qc.gds.InvoiceGeneratedFacade.doOrchestrate(InvoiceGeneratedFacade.java:151)
at com.buggycompany.framework.gdstask.BaseGDSFacade.orchestrate(BaseGDSFacade.java:32)
at com.buggycompany.framework.gdstask.BaseGDSFacade.doWork(BaseGDSFacade.java:22)
at com.buggycompany.framework.concurrent.BuggycompanyCallable.call(buggycompanyCallable.java:80)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
1 2 3 4 5
6
7
1 Thread Name - InvoiceThread-A996
2 Priority - Can have values from 1 to 10
3
Thread Id - 0x00002b7cfc6fb000 – Unique ID assigned by JVM. It's returned by calling the Thread.getId() method.
4 Native Id - 0x4479 - This ID is highly platform dependent. On Linux, it's the pid of the thread. On Windows, it's simply the OS-level thread ID within
a process. On Mac OS X, it is said to be the native pthread_t value.
5 Address space - 0x00002b7d17ab8000 -
6 Thread State - RUNNABLE
7 Stack trace -

6 thread states
RUNNABLE
TERMINATED
NEW
TIMED_WAITING
Thread.sleep(10);
WAITING03
02
01
06
05
public void synchronized getData() {
makeDBCall();
}
BLOCKED
04
Thread 1: Runnable
Thread 2: BLOCKED
wait();
Thread 1: Runnable

Step 4: Identify lines of code causing CPU spike
Thread Ids: 31306, 31307, 31308
High CPU consuming Threads Ids reported in ‘top –H’.
Let’s look up these thread Ids in Thread dump
HexaDecimal equivalent:
• 31306  7a4a
• 31307  7a4b
• 31308  7a4c

1: package com.buggyapp.cpuspike;
2:
3: /**
4: *
5: * @author Test User
6: */
7: public class Object1 {
8:
9: public static void execute() {
10:
11: while (true) {
12:
13: doSomething();
14: }
15: }
16:
17: public static void doSomething() {
18:
19: }
20: }
Source code

‘Free’ Thread dump analysis tools
https://developer.ibm.com/javas
dk/tools/
IBM Thread & Monitor analyzerSamuraiFastThread
http://fastThread.io/ http://samuraism.jp/samurai/en/in
dex.html
Visual VM
https://visualvm.github.io/
Freely available Thread dump analysis tools
030201
04

Analysis with tool
Generated visual report

Real problem in a major trading application

Unable to create new native thread
Troubleshooting OutOfMemoryError

Major financial institution in N. America
Thread dump troubleshooting pattern: RSI
https://map.tinyurl.com/yxho6lan

Java Heap + metaspace
Physical memory
Java Heap + metaspace
Physical memory
Process-
1
Process-
2
Key: Threads are created outside heap
threads
Solution:
1. Fix thread leak
2. Increase the Thread Limits Set at
Operating System(ulimit –u)
3. Reduce Java Heap Size
4. Kills other processes
5. Increase physical memory size
6. Reduce thread stack size (-Xss).
Note: can cause StackOverflowError
OOM: Unable to create new native thread

8 types - OutOfMemoryError
Java heap space
https://blog.gceasy.io/2015/09/25/outofmemoryerror-beautiful-1-page-document/
01
GC overhead limit exceeded
02
Requested array size exceed VM limit
03
Permgen space
04
Metaspace
05
Unable to create new native thread
06
Kill process or sacrifice child
07
reason stack_trace_with_native method
08
java.lang.OutOfMemoryError: <type>

• https://tinyurl.com/yywdmvyy
• RSI Pattern – Same pattern, different problem.
Troubleshooting unresponsive app

Thread dump analysis Patterns
https://blog.fastthread.io/category/thread-dump-patterns/
Leprechaun PatternTreadmill PatternRSI Pattern
Athlete PatternTraffic Jam PatternAll Roads leads to Rome
Pattern
few more …Several Scavengers PatternAtherosclerosis Pattern

Troubleshooting Memory
problems

Enable GC Logs (always)
Till Java 8:
-XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:<file-path>
From Java 9:
-Xlog:gc*:file=<file-path>

‘Free’ GC Log analysis tools
https://developer.ibm.com/javas
dk/tools/
IBM GC & Memory visualizerGC Viewer
https://github.com/chewiebug/G
CViewer
GCeasy
http://gceasy.io/
Google Garbage cat (cms)
https://code.google.com/archiv
e/a/eclipselabs.org/p/garbagec
at
HP Jmeter
https://h20392.www2.hpe.com/
portal/swdepot/displayProductI
nfo.do?productNumber=HPJM
ETER
Freely available Garbage collection log analysis tools
030201
0504

Corresponding – Reclaimed bytes chart

How to diagnose memory leak?
Capture heap dumps
jmap -dump:live,file=<file-path> <pid>
Example: jmap -dump:live,file=/opt/tmp/AddressBook-heapdump.bin 37320
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/logs/heapdump
Eclipse MAT, HeapHero
Two good tools to analyze memory leaks

Capture heap dumps
option.
jVisualVMHeapDumpOnOutOfMemoryError
-XX:+HeapDumpOnOutOfMemoryError -
XX:HeapDumpPath=<file-path>
jmap (since Java 5)
jmap -dump:live,file=<file-path> <pid>
Few APM Tools does provide this support
APM ToolsThreadMXBean
Programmatic way to capture thread
dumps
https://blog.fastthread.io/2016/06/06/how-to-take-thread-dumps-7-options/
030201
0605
If you are using WAS, this option can be
used
IBM administrative console
jcmd <pid> GC.heap_dump <file-path>
Jcmd (since Java 7)
04
07

Micro-metrics
https://blog.gceasy.io/2019/03/13/micrometrics-to-forecast-application-performance/

Macro-Metrics
Can’t forecast scalability, availability, performance problems
CPU
RESPONSE
TIME
MEMORY

Micro-metrics: Early Indicators
Repeated Full GCs happens here
OutOfMemoryError happens here

File Descriptors
File descriptor is a handle to access: File, Pipe,
Network Connections. If count grows it’s a lead
indicator that application isn’t closing resources
properly.
Few more…
TCP/IP States, Hosts count, IOPS, ..
Thread States
If BLOCKED thread state count grows, it’s
an early indication that your application has
potential to become unresponsive
GC Throughput
Amount time application spends in processing
customer transactions vs amount of time application
spend in doing GC
Object Reclamation rate
If number of objects created in unit time
GC Latency
If pause time starts to increase, then
it’s an indication that app is suffering
from memory problems
What are Micrometrics?
https://blog.gceasy.io/2019/03/13/micrometrics-to-forecast-application-performance/

GC Log
netstat vmstat
Thread Dumps
dmesg
Heap Dumps
What data to capture?
ps
top -H
Disk Usage
top
IBM Script: https://map.tinyurl.com/y4gz6o7q
Captures all of the above artifacts

Thank you my friends!
Ram Lakshmanan
ram@tier1app.com
@tier1app
https://www.linkedin.com/company/gceasy

Troubleshooting real production problems

More Related Content

What's hot (20)

Similar to Troubleshooting real production problems (20)

More from Tier1 app (20)

Recently uploaded (20)

Troubleshooting real production problems