322 CHAPTER 12 TRENDING, FORECASTING, AND CAPACITY (Yahoo free web hosting)
322 CHAPTER 12 TRENDING, FORECASTING, AND CAPACITY PLANNING Figure 12-1. Because the application calls get() on the Collections class, a new reference is returned to the application. When the application discards the reference, the Collections class continues to maintain its reference to the object; hence, the object cannot be garbage collected. Memory leaks are typically subtle and may take days or even weeks to crash an application server. In order to detect a potential memory leak, you need to analyze your heap utilization, specifically the heap utilization valleys. As objects are created and destroyed, the heap utilization oscillates, so its utilization has peaks and valleys. If the valleys are consistently increasing, then the application is allocating more memory than it is freeing, and you can draw one of the following three conclusions: The application is approaching its steady state, and the increasing trend is just indicative of natural growth. Your heap is too small to support the requirements of the application; the heap should eventually level off, but your heap is too small to do so. You have a memory leak. Figure 12-2 illustrates the behavior of a heap that might be experiencing a memory leak.
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.