Debugging java deployments_2

Rohit KelapureIBM Advisory Software Engineer 29 September 2011Server Resiliency - Debugging Java deployments

Introduction to Speaker – Rohit KelapureResponsible for the resiliency of WebSphere Application ServerTeam Lead and architect of Caching & Data replication features in WebSphereCalled upon to hose down fires & resolve critical situationsCustomer advocate for large banks Active blogger All Things WebSphereApache Open Web Beans committer Java EE, OSGI & Spring Developerkelapure@us.ibm.comkelapure@gmail.comLinkedinhttp://twitter.com/#!/rkela2

Important DisclaimersTHE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILST EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. ALL PERFORMANCE DATA INCLUDED IN THIS PRESENTATION HAVE BEEN GATHERED IN A CONTROLLED ENVIRONMENT. YOUR OWN TEST RESULTS MAY VARY BASED ON HARDWARE, SOFTWARE OR INFRASTRUCTURE DIFFERENCES.ALL DATA INCLUDED IN THIS PRESENTATION ARE MEANT TO BE USED ONLY AS A GUIDE.IN ADDITION, THE INFORMATION CONTAINED IN THIS PRESENTATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM, WITHOUT NOTICE. IBM AND ITS AFFILIATED COMPANIES SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF: - CREATING ANY WARRANT OR REPRESENTATION FROM IBM, ITS AFFILIATED COMPANIES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS3

Copyright and Trademarks© IBM Corporation 2011. All Rights Reserved. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., and registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web – see the IBM “Copyright and trademark information” page at URL: www.ibm.com/legal/copytrade.shtml4

OutlineServer Resiliency FundamentalsCommon JVM ProblemsProtecting your JVMHung thread detection, Thread Interruption, Thread hang recoveryMemory leak detection, protection & actionScenario based problem resolutionToolingEclipse Memory AnalyzerThread Dump AnalyzerGarbage Collection and Memory Visualizer5

ResiliencyProperty of a material that can absorb external energy when it is forced to deform elastically, and then be able to recover to its original form and release the energy6

Server Resiliency Concepts7October 4, 2011Explicit MessagingDistributed Shared memory – Better ConsistencyMessage Passing – Loose CouplingUniform InterfaceE.g. World Wide WebBetter scalability, reusability and reliability Data, process and other forms of computations identified by one mechanism Semantics of operations in messages for operating on the data are unifiedSelf ManagementComposed of self-managing components.Managed element, managers, sensors & effectorse.g. TCP/IP Congestion ControlRedundancy (Data and processing)Create ReplicasHigh cost of initialization and reconfigurationRedundant elements need to be synchronized from time to timePartitionSplitting the data into smaller pieces and storing them in distributed fashionAllows for parallelization & divide and conquerPartial failure isolationVirtualizationFunctionalities of processing and data element virtualized as a serviceLoose coupling between system and consumed servicesIntegration by enforcing explicitly boundary and schema-based interfacesDecentralized Control High communication overhead of centralized control for a system of heavy redundancySometimes trapped in locally optimized solutionsFixing issues requires shutting down the entire system e.g. AWS outage

Most common JVM Problem Scenarios8October 4, 2011

Thread HangsThreading and synchronization issues are among the top 5 application performance challengestoo aggressive with shared resources causes data inconsistenciestoo conservative leads to too much contention between threads Application unresponsiveness Adding users / threads /CPUs causes app slow down (less throughput, worse response)High lock acquire times & contentionRace conditions, deadlock, I/O under lockTooling is needed to rescue applications and the JVM from itself Identify these conditions If possible remedy them in the short term for server resiliency9October 4, 2011

JVM Hung Thread Detection Every X seconds an alarm thread wakes up and iterates over all managed thread pools. Subtract the "start time" of the thread from the current time, and passes it to a monitor. Detection policy then determines based on the available data if the thread is hung Print stack trace of the hung thread10October 4, 2011

Thread Interruption 101 Thread.stop stops thread by throwing ThreadDeath exception * DeprecatedThread.interrupt(): Cooperative mechanism for a thread to signal another thread that it should, at its convenience and if it feels like it, stop what it is doing and do something else.Interruption is usually the most sensible way to implement task cancellation. Because each thread has its own interruption policy, you should not interrupt a thread unless you know what interruption means to that thread.Any method sensing interruption shouldAssume current task is cancelled & perform some task‐specific cleanupExit as quickly and cleanly as possible ensuring that callers are aware of cancellation Propagate the exception, making your method an interruptible blocking method, to throw new InterruptedException()Restore the interruption status so that code higher up on the call stack can deal with it Thread.currentThread().interrupt()Only code that implements a thread's interruption policy may swallow an interruption request. 11October 4, 2011

13October 5, 2011CancellingThreads

Dealing with Non‐interruptible BlockingMany blocking library methods respond to interruption by returning early and throwing InterruptedExceptionMakes it easier to build tasks that are responsive to cancellation Lock.lockInterruptiblyThread.sleep,Thread.waitThread.notifyThread.joinNot all blocking methods or blocking mechanisms are responsive to interruptionif a thread is blocked performing synchronous socket I/O, interruption has no effect other than setting the thread's interrupted statusIf a thread is blocked waiting for an intrinsic lock, there is nothing you can do to stop short of ensuring that it eventually acquires the lock14October 4, 2011

Thread Hang Recovery – Technique Application specific hacks for thread hang recoveryByte code instrumentationTransform the concrete subclasses of the abstract classes InputStream& OutputStreamto make the socket I/O operations interruptible. Transform an application class so that every loop can be interrupted by invoking Interrupter.interrupt(Thread, boolean)Transform a monitorenter instruction and a monitorexit instruction so that the wait at entering into a monitor is interruptiblehttp://www.ibm.com/developerworks/websphere/downloads/hungthread.html15

Memory LeaksLeaks come in various types, such asMemory leaksThread and ThreadLocal leaksClassLoader leaksSystem resource leaks Connection leaksCustomers want to increase application uptime without cycling the server. Frequent application restarts without stopping the server.Frequent redeployments of the application result in OOM errors What do we have today Offline post-mortem analysis of a JVM heap. Tools like Jrockit Mission Control, MAT. IEMA are the IBM Extensions for Memory AnalyzerRuntime memory leak detection using JVMTI and PMI (Runtime Performance Advisor)We don’t have application level i.e. top down memory leak detection and protectionLeak detection by looking at suspect patterns in application code16October 4, 2011

ClassLoader Leaks 101A class is uniquely identified byIts name + The class loader that loaded itClass with the same name can be loaded multiple times in a single JVM, each in a different class loaderWeb containers use this for isolating web applicationsEach web application gets its own class loaderReference ChainAn object retains a reference to the class it is an instance ofA class retains a reference to the class loader that loaded itThe class loader retains a reference to every class it loadedRetaining a reference to a single object from a web application pins every class loaded by the web applicationThese references often remain after a web application reload With each reload, more classes get pinned ultimately leading to an OOM17October 4, 2011

Tomcat pioneered approach - Leak Prevention JRE triggered leak Singleton / static initializerCan be a ThreadSomething that won’t get garbage collectedRetains a reference to the context class loader when loadedIf web application code triggers the initializationThe context class loader will be web application class loaderA reference is created to the web application class loaderThis reference is never garbage collectedPins the class loader (and hence all the classes it loaded) in memoryPrevention with a DeployedObjectListenerCalling various parts of the Java API that are known to retain a reference to the current context class loaderInitialize these singletons when the Application Server’s class loader is the context class loader18October 5, 2011

Leak DetectionApplication Triggered LeaksClassLoader ThreadsThreadLocal JDBC DriversNon ApplicationRMI TargetsResource BundleStatic final referencesInstrospectionUtilsLoggersPreventionCode executes when a web application is stopped, un-deployed or reloadedCheck, via a combination of standard API calls and some reflection tricks, for known causes of memory leaks19October 4, 2011

Memory leak detection console20October 4, 2011

What is wrong with my application …?Why does my application run slow every time I do X ?Why does my application have erratic response times ? Why am I getting Out of Memory Errors ?What is my applications memory footprint ?Which parts of my application are CPU intensive ?How did my JVM vanish without a trace ?Why is my application unresponsive ?What monitoring do I put in place for my app. ?21October 4, 2011

What is your JVM up to ?Windows style task manager for displaying thread status and allow for their recovery & interruptionLeverage the ThreadMXBean API in the JDK to display thread informationhttps://github.com/kelapure/dynacache/blob/master/scripts/AllThreads.jsphttps://github.com/kelapure/dynacache/blob/master/scripts/ViewThread.jsp22October 4, 2011

Application runs slow when I do XXX ?Understand impact of activity on componentsLook at the thread & method profiles IBM Java Health Center Visual VMJrockit Mission ControlJVM method & dump trace - pinpoint performance problems. Shows entry & exit times of any Java methodMethod to trace to file for all methods in tests.mytest.packageAllows taking javadump, heapdump, etc when a method is hitDump javacore when method testInnerMethod in an inner class TestInnerClass of a class TestClass is calledUse Btrace, -Xtrace * –Xdump to trigger dumps on a range of eventsgpf, user, abort, fullgc, slow, allocation, thrstop, throw …Stack traces, tool launching23October 4, 2011

Application has erratic response times ?Verbose gc should be enabled by default<2% impact on performanceVisualGC, GCMV &PMAT : Visualize GC output In use space after GCPositive gradient over time indicates memory leakIncreased load (use for capacity plan) Memory leak (take HDs for PD.) Choose the right GC policy Optimized for “batch” type applications, consistent allocation profileTight responsiveness criteria, allocations of large objectsHigh rates of object “burn”, large # of transitional objects12, 16 core SMP systems with allocation contention (AIX only)GC overhead > 10%  wrong policy | more tuningEnable compressed references for 64 bit JVM 24October 5, 2011

Out Of Memory Errors ?JVM Heap sized incorrectlyGC adapts heap size to keep occupancy [40, 70]%Determine heap occupancy of the app. under loadXmx = 43% larger than max. occupancy of app.For 700MB occupancy , 1000MB Max. heap is reqd. (700 +43% of 700)Analyze heapdumps & system dumps with tools like Eclipse Memory AnalyzerLack of Java heap or Native heapEclipse Memory Analyzer and IBM extensions Finding which methods allocated large objectsPrints stacktrace for all objects above 1KEnable Java Heap and Native heap monitoring JMX and metrics output by JVMClassloader exhaustion25October 4, 2011

Applications memory footprint ?HPROF – profiler shipped with JDK – uses JVMTI Analysis of memory usage -Xrunhprof:heap=all Performance Inspector tools - JPROF Java Profiling AgentCapture state of the Java Heap later processed by HDUMPGroup a system dump by classloadersince each app has its own classloader, you can get accurate information on how much heap each application is taking upUse MAT to investigate heapdumps & system dumps Find large clumps, Inspect those objects, What retains them ?Why is this object not being garbage collected – List Objects > incoming refs, Path to GC roots, Immediate dominators Limit analysis to a single application in a JEE environment - Dominator tree grouped by ClassLoader Dominator tree grouped by Class LoaderSet of objects that can be reclaimed if we could delete X - Retained Size Graphs Retained Size Graphs Traditional memory hogs like HTTPSession, Cache - Use Object Query Language (OQLUse Object Query Language (OQL)26October 4, 2011

Using Javacores for TroubleshootingJavacores are often the most critical piece of information to resolve a hang, high CPU, crash and sometimes memory problemsA Javacore is a text file that contains a lot of useful informationThe date, time, java™ version, full command path and argumentsAll the threads in the JVM, including thread state, priority, thread ID, nameThread call stacksJavacores can be generated automatically or on demandAutomatically when an OutOfMemoryException is thrownOn demand with “kill -3 <pid>” Message to the SystemOut when a javacore is generated27"WebContainer : 537" (TID:0x088C7200, sys_thread_t:0x09C19F00, state:CW, native ID:0x000070E8) prio=5 at java/net/SocketInputStream.socketRead0(Native Method) at java/net/SocketInputStream.read(SocketInputStream.java:155) at oracle/net/ns/Packet.receive(Bytecode PC:31) at oracle/net/ns/DataPacket.receive(Bytecode PC:1) at oracle/net/ns/NetInputStream.read(Bytecode PC:33) at oracle/jdbc/driver/T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1123) at oracle/jdbc/driver/T4C8Oall.receive(T4C8Oall.java:480) at oracle/jdbc/driver/T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:813) at oracle/jdbc/driver/OracleStatement.doExecuteWithTimeout(OracleStatement.java:1154) at oracle/jdbc/driver/OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3415)at com/ibm/commerce/user/objects/EJSJDBCPersisterCMPDemographicsBean_2bcaa7a2.load() at com/ibm/ejs/container/ContainerManagedBeanO.load(ContainerManagedBeanO.java:1018) at com/ibm/ejs/container/EJSHome.activateBean(EJSHome.java:1718)

CPU intensive parts of the app?ThreadDumps or Javacores- Poor mans profilerPeriodic javacoresThread analysis – using the Thread Monitor Dump Analyzer toolHigh CPU is typically diagnosed by comparing two key pieces of informationUsing Javacores, determine what code the threads are executingGather CPU usage statistics by threadFor each Javacore compare the call stacks between threadsFocus first on Request processing threads firstAre all the threads doing similar work? Are the threads moving ?Collect CPU statistics per threadIs there one thread consuming most of the CPU?Are there many active threads each consuming a small percentage of CPU?High CPU due to excessive garbage collection ?If this is a load/capacity problem then use HPROF profiler -Xrunhrof:cpu=samples, -Xrunhprof:cpu=time28October 4, 2011

Diagnosis - HangsOften hangs are due to unresponsive synchronous requestsSMTP Server, Database, Map Service, Store Locator, Inventory, Order processing, etc3XMTHREADINFO "Servlet.Engine.Transports : 11" (TID:0x7DD38040, sys_thread_t:0x44618828, state:R, native ID:0x4A9F) prio=54XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.SQLExecute()4XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(DB2PreparedStatement.java)4XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java()4XESTACKTRACE at ...3XMTHREADINFO "Servlet.Engine.Transports : 12" (TID:0x7DD37FC0, sys_thread_t:0x4461BDA8, state:R, native ID:0x4BA0) prio=54XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.SQLExecute()4XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(DB2PreparedStatement.java)4XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java()4XESTACKTRACE at ...3XMTHREADINFO "Servlet.Engine.Transports : 13" (TID:0x7DD34C50, sys_thread_t:0x4465B028, state:R, native ID:0x4CCF) prio=54XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.SQLExecute()4XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(DB2PreparedStatement.java)4XESTACKTRACE at COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java()Not all hangs are waiting on an external resourceA JVM can hang due to a synchronization problem - One thread blocking several others293XMTHREADINFO "Servlet.Engine.Transports : 11" (TID:0x7DD38040, sys_thread_t:0x44618828, state:R, native ID:0x4A9F) prio=53LKMONOBJECT com/ibm/ws/cache/Cache@0x65FB8788/0x65FB8794: owner "Default : DMN0" (0x355B48003LKWAITERQ Waiting to enter:3LKWAITER "WebContainer : 0" (0x3ACCD000)3LKWAITER "WebContainer : 1" (0x3ACCCB00)3LKWAITER "WebContainer : 2" (0x38D68300)3LKWAITER "WebContainer : 3" (0x38D68800)

How did my JVM vanish without trace ?JVM Process Crash Usual Suspects Bad JNI calls, Segmentation violations, Call Stack OverflowNative memory leaks - Object allocation fails with sufficient space in the JVM heapUnexpected OS exceptions (out of disk space, file handles), JIT failuresMonitor the OS process size Runtime check of JVM memory allocations –Xcheck:memoryNative memory usage - Create a core dump on an OOMJNI code static analysis -Xcheck:jni (errors, warnings, advice)GCMV provides scripts and graphing for native memoryWindows “perfmon“, Linux “ps” & AIX “svmon” Find the last stack of native code executing on the thread during the crashThe signal info (1TISIGINFO) will show the Javacore was created due to a crashSignal 11 (SIGSEGV) or GPF30October 4, 2011

What do I monitor ?31October 4, 2011

Top Malpractices32October 4, 2011

Support Assistant Workbench to help with Problem Determination33October 4, 2011

One stop shop for tools to analyze JVM issues34October 4, 2011

Runtime Serviceability aidsTroubleshooting panels in the administration consolePerformance Monitoring Infrastructure metrics Diagnostic Provider MbeansDump Configuration, State and run self-testApplication Response Measurement/Request Metrics Follow transaction end-to-end and find bottlenecksTrace logs & First Failure Data CaptureRuntime Performance AdvisorsMemory leak detection, session size, …Specialized tracing and Runtime checksTomcat Classloader Leak DetectionSession crossover, Connection leak, ByteBuffer leak detection Runaway CPU thread protection36October 4, 2011

References Java theory and practice: Dealing with InterruptedExceptionhttp://www.ibm.com/developerworks/java/library/j-jtp05236/index.htmlArchitectural design for resiliencehttp://dx.doi.org/10.1080/17517570903067751IBM Support Assistanthttp://www-01.ibm.com/software/support/isa/download.htmlHow Customers get into troublehttp://www-01.ibm.com/support/docview.wss?uid=swg2700835937

Debugging java deployments_2

Recommended

More Related Content

What's hot (18)

Similar to Debugging java deployments_2 (20)

More from Rohit Kelapure (20)

Recently uploaded (20)

Debugging java deployments_2

Editor's Notes