Trustin Lee wrote: > > I opened the hprof files you provided in YourKit profiler and it seems > like the actual amount of memory the JVM is very small: > > http://www.nabble.com/file/p13891096/avis-profiler-report.zip > avis-profiler-report.zip > > I often observe JVM increases its total heap size too much even when the > application doesn't demand that much. Wouldn't it be such a case? >
OK, now I'm really confused. Am I reading the output of the jmap -histo output wrong? The output I cited in the original mail seemed to be saying there were 2,192,677 instances of java.util.concurrent.ConcurrentLinkedQueue$Node, taking up 35,082,832 bytes. And 8,285 byte arrays taking up 23,427,664 bytes. Which seems excessive for a server with just 20 connections, to put it mildly. But, as you say, the reports that YourKit generated don't bear this out (although that output is not from the exact same instance as the hprof's, it was taken earlier in my testing). Probably the best thing is to re-run the server with heap allocation on, let it run for a few days, and jmap it again to generate both a histogram and a hprof. Thanks for your help so far, Matthew. -- View this message in context: http://www.nabble.com/Memory-leak-in-MINA-1.1.4-tf4849077s16868.html#a13891490 Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
