search : heap dump

2608641 CF-4038087 External U. E-mail sent with access details for PRODUCTION heap dump created yesterday, and jvm.config.

2608639 CF-4038865 External U. I was finally able to catch both a thread dump and heap dump of the failure happening. When it happens the system typically has a bunch of BLOCKERS and WAIT threads sitting around for 30 seconds. All of the other threads that are blocked do nothing making all

2608578 CF-4060624 External U. https://www.hass.de/content/coldfusion-10-macromedia-database-drivers-leaking-memory Another example of someone else having similar issue. I didn't have all his heap dump tools, but our graphs and results are about the same. This issue has now occured on another

this issue. -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=${DOMAIN_HOME}/logs/ Please share your jvm.config file as well. You can send jvm.config file at nimsharm@adobe.com. Regards, Nimit

3015864 CF-4198534 Jonas M. We are seeing a steady increase of the memory used on CF2016 with update 3. Loading a heap dump in Eclipse Memory Analyzer shows that 70% (3.4 GB) is consumed by org.mozilla.javascript.NativeObject.

2673675 CF-4118893 Nimit S. Aaron, GrootClassLoader is used to load all necessary classes only related to API Manager into the JVM. We would like to help if you encounter such a scenario. Please share the information mentioned below if you encounter such a scenario: 1. jvm.config file 2. heap

[…] The post Thread Dump Analysis using Performance Monitoring Toolset appeared first on ColdFusion. Blog,Uncategorized,garbage Collection,Heap dump,Performance enhancement,Thread dump

of continuous use. Steps to Reproduce: Simplest reproduction case is to run this: Do a heap dump, and search the heap dump for instances of coldfusion.util.key. There will be 1,000,000 there and they will never get cleaned up. Actual Result: There will be 1,000,000+ instances of java

2608513 CF-4073011 Database Michael Littleton deleteonexithook filling memory Duplicate ID: CF-4038087 Problem Description: On a long running server, memory will continue to be consumed by the "deleteonexithook" in java. Upon heap dump, this will contain millions of records to non-existent files

dump just after initializing the server. Then I run this code several times and see the tenured generation fill through jConsole. After, I run another heap dump. Using Eclipse Memory Analysis Tool's Leak report I can see one large object rooted on `coldfusion.util.Key`. Result

2608641 CF-4038087 External U. We have supplied Adobe with a heap dump, jvm.config, a stripped website, and a stripped database. The website has one functioning page - it does nothing but connect to the database and perform a simple query. The one page load leaves one java

.key.util still exists in 9.02 and we cannot apply the hotfix hf901-3119991.jar to 9.02 Steps to Reproduce: Take a heap dump of the server that is running out of heap space and observe 1GB+ of coldfusion.key.util classes. OR - decompile CFusion.jar and observe that coldfusion.key.util is using strong

and a couple of times we got out-of-memory errors which sent us down this track. We increased memory to extend the uptime but eventually caught up again. finally investigated the heap dump and found multiple (millions) of instances of the org.mozilla.javascript.NativeObject using about 90% of memory

2596973 CF-3286878 External U. A function needs to be executed on the cfc for it to start using memory, seems like its lazy-initialized. Is using upto about 2 gigabytes of memory on CF9. And almost nothing on CF8. I analyzed a heap dump in eclipse memory analysis tool (MAT). All the cfc

flight recording for CF8 and CF9 (you will need JRockit to view: (http://www.oracle.com/technetwork/middleware/jrockit/downloads/index.html), as well as a heap dump for CF9. Please pay special attention to snapshots of JRockit Mission control noting the type and size of objects in CF9 relative to those

.ex. If you take a heap dump with jmap and then look at it with jhat or something easier like VisualVM you’ll see that there are 10000 instances of coldfusion.tagext.lang.LockTag and 10000 instances of coldfusion.tagext.lang.LogTag.These instances will NEVER go away until the thread ends.I’ve reproduced

" {} }; } // Call the closure one million times. for (i = 1; i Now take a heap dump and analyze it. There will be 5 million instances of coldfusion.tagext.lang.LockTag in memory whose GC roots go through the closure. See the attached image. The path is: CF_ANONYMOUSECLOSURE inner class > invokePage (CFDummy

and not being removed until you hit a max. This is causing memory issues on my server. I also suspect that there may be a memory leak in the jvm heap related to all of this. I haven't gotten proof yet, but I did a heap dump with JProfiler and I had about 5G's of charts in memory. Even if I maxed out my Max

there. You could also use jvm tools to obtain thread dumps and do heap analysis or profiling. Or you can use tools created for CFers that facilitate doing some or all of those things, and even more. In cf8-2016 enterprise, we have the CF server monitor. In cf2018 (standard or enterprise edition) we

()# Actual Result: ColdFusion will eventually run out of heap because the large page buffer (1,048,600bytes) cannot be garbage collected. By inspecting Heap Dump in Visual VM, sort by size (descending) in Classes: 1. Double click the first one, which should be `byte[]` 2. In the left Instances panel, sort

3960347 CF-4201076 Piyush K. Ken/Charlie, Can you pls. share some specifics. What is the max, min and metaspace size of your JVM heap. How long does it take for you to run into a "GC limit exceeded" error? What classes involved in collecting debugging did you see in the thread dump (pls share

| Shallow Heap | Retained Heap | Percentage

.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Unknown Source) at java.io.CharArrayWriter.write(Unknown Source) at coldfusion.runtime.CharBuffer.replace(CharBuffer.java:37) at coldfusion.runtime.CharBuffer.replace(CharBuffer.java:50) at coldfusion.runtime.NeoBodyContent.write(NeoBodyContent.java:254