tracker issue : CF-3042197

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 84259:(Watson Migration Closure)When running long running jobs (Scheduled Tasks) that process thousands of documents, if the Server Monitor's "Monitoring" & "Profiling" features are enabled, the JVM will quickly consume all availabl

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/

Reporter/Name(from Bugbase): Steven Erat / Steven Erat (StevenErat)

Created: 09/17/2010

Components: Server Monitoring

Versions: 9.0.1

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Major / Unknown

Locale/System: English / Win All

Vote Count: 8

Problem:

When running long running jobs (Scheduled Tasks) that process thousands of documents, if the Server Monitor's "Monitoring" & "Profiling" features are enabled, the JVM will quickly consume all available memory within a few minutes.  On a 64 bit installation, the app normally uses about 1.5 GB, but the max heap is 12GB.  In this scenario, in 3 minutes the memory will grow until it approaches the max heap size and then begin to report java.lang.OutOfMemoryError Java heap space, and GC Overhead Limit Exceeded.Note that the Memory Tracking feature was always disabled.  This is reproducible with just Monitoring and Profiling on.  When we turn off all monitoring, the scheduled task is able to complete without a huge memory consumption.  We can again reproduce the memory problem by turning M&P back on.There is an excellent blog post on the topic on the mxunit blog showing that milions of CFStackFrame objects were in the heap.  http://blog.mxunit.org/2010/01/using-eclipse-mat-to-track-down.html
Method:

Cannot provide test code.  Our scheduled task is a complex application that instanstiates a variety of helper CFCs.  It is database centric.   Problem is reproducible when SM M&P is enabled
Result:

Exception thrown by error-handling template:java.lang.OutOfMemoryError: Java heap space        at coldfusion.monitor.stack.CFStackFrame.copy(CFStackFrame.java:166)        at coldfusion.monitor.stack.CFStackFrame.<init>(CFStackFrame.java:61)        at coldfusion.monitor.stack.CFStackFrame.copy(CFStackFrame.java:166)        at coldfusion.monitor.stack.CFStackFrame.<init>(CFStackFrame.java:61)        at coldfusion.monitor.stack.CFStackFrame.copy(CFStackFrame.java:166)        at coldfusion.monitor.stack.CFStackFrame.<init>(CFStackFrame.java:61)        at coldfusion.monitor.stack.CFStackFrame.copy(CFStackFrame.java:166)        at coldfusion.monitor.stack.CFStackFrame.<init>(CFStackFrame.java:61)        at coldfusion.monitor.stack.CFStackFrame.copy(CFStackFrame.java:166)        at coldfusion.monitor.stack.CFStackFrame.<init>(CFStackFrame.java:61)        at coldfusion.monitor.stack.CFStackFrame.copy(CFStackFrame.java:166)        at coldfusion.monitor.stack.CFStackFrame.<init>(CFStackFrame.java:61)        at coldfusion.monitor.stack.CFStackFrame.copy(CFStackFrame.java:166)        at coldfusion.monitor.stack.CFStackFrame.<init>(CFStackFrame.java:61)

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3042197

External Customer Info:
External Company:  
External Customer Name: Steven Erat
External Customer Email: 722B2D4444633DB6992016B6
External Test Config: 09/17/2010

Attachments:

Comments: