International Business Machines Corporation

Robbie John Minshall

Matt Richard Hogstrom

Carolyn Haibt Norton

Bert Vincent Laonipon

Srinvasan K Rangaswamy

Ruth Edith Willenborg

Detecting leaky memory during the execution of an application in a data processing system. A memory controller identifies a leaky section of memory and delegates to an allocation component to allocate more memory. An isolator component isolates the memory section and further divides the memory section into subsections. Each section and each subsection are tested to determine if memory resources are strained to identify an application or its component causing the strain. Each section and subsection are further divided and isolated until the leaky portion of memory is identified, and as a result, the software component causing the leak can also be identified.

Software memory leak analysis using memory isolation

A method in a data processing system for detecting and reducing database contention and deadlock caused from within an application server. A determination is made as to whether a set of parameters in a statistical model indicates contention. If the set of parameters in the statistical model indicates contention, an application server administrator is notified of the contention and the number of threads in an application server pool is reduced. If the set of parameters in the statistical model indicates contention is reduced, the number of threads in the application server pool is increased.

Database contention and deadlock detection and reduction within application servers

A computerized method, program product, and a service that allocates and isolates leaky memory during the execution of an application in a data processing system. A memory controller having several components first identifies a leaky section of memory and delegates to an allocation component to allocate more memory if possible. If, however, the problematic memory section should not be allocated more memory, an isolator component can isolate the memory section and further divide the memory section into subsections and so on. Each section and each subsection may then be tested to determine if more memory can be allocated, tested to determine if memory resources are strained so as to identify the application or its component causing the strain and then binding the memory. Each section and subsection and further divided and isolated until the leaky portion of memory is identified, and as a result, the software component causing the leak can also be identified. The software component associated with the leaky memory section or subsection can also be taken out-of-service.

The present invention provides a method, system, and computer program product for light weight memory leak detection. A method in accordance with an embodiment of the present invention comprises: obtaining raw free memory statistics; approximating free memory after garbage collection from the raw free memory statistics; and analyzing the approximated free memory after garbage collection to identify a potential memory leak. A method in accordance with another embodiment of the present invention comprises the steps of: obtaining raw free memory statistics; generating a vector of memory leak indicators from the raw free memory statistics; comparing the vector of memory leak indicators against a plurality of vectors of the same memory leak indicators for known memory leak scenarios; and identifying a potential memory leak based on the comparison.

Growing community of inventors

Chapel Hill, NC, United States of America

Robbie John Minshall