Detecting Memory Leaks in Applications Spanning Multiple JVMs

Invariably, when your company is in a crunch situation for getting a product released, your application infrastructure will hang up or fail, thus delaying the rollout. This can be disastrous, because the reason for the rollout is usually essential fixes and features necessary to remain competitive. A major cause of such problems is unchecked resource allocation, otherwise referred to as a leak. This session takes a look at abnormal versus normal resource allocation behavior in Java Virtual Machine (JVM) applications and how to detect abnormal behavior as early as possible.

Copyright © 2013 Oracle and/or its affiliates. Oracle® is a registered trademark of Oracle and/or its affiliates. All rights reserved. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the "Materials"). The Materials are provided "as is" without any warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.