We played with some of the jvm settings, and ran a program that normally times out, it's a huge extract, pretty sure badly coded.
It now works, still not fast, but doesn't time out. Now to look through that code and see how to make it better Regards Dale Fraser http://dale.fraser.id.au http://cfmldocs.com <http://cfmldocs.com/> http://learncf.com http://flexcf.com From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf Of charlie arehart Sent: Thursday, 26 August 2010 9:43 AM To: cfaussie@googlegroups.com Subject: RE: [cfaussie] Bad Error Thanks for the shout out Mr B. I'm afraid I've been detained the past couple of days so am just catching up on this thread. Sounds like Dale's got stuff to go on, so will look forward to hearing what he has to say. I will note just a couple of additional thoughts: it's possible that this page was a victim rather than the culprit (something else was causing the jvm to be unable to recover much during GC). Also, that JVM tuning page focuses on disabling the feature rather than fixing the problem, which is too bad. Similarly, on this broad subject of finding solutions to JVM issues, beware that sometimes the docs (or blogs/articles) focus on solving problems with Java where the application is a single-use custom-built app, whereas of course CF is a multi-purpose, multi-threaded app which we have no control over (even in our CFML that we write), so you have to be cautious of some of the recommendations out there. Worse still, some recommendations are relevant to JVM 1.4 (which is what CF 6 and 7 ran on) while things in the JVM changed quite a bit in 1.5 and 1.6 (and CF 8 and 9 run on the latter). It's a bit of a shame that we sometimes have to delve into the dark corners of jvm-related problem solving, but when we do, we should be cautious about confirming that what we read does apply to our current environment. But last, and perhaps most important, is that often the JVM errors and their recommended resolutions focus on making the error go away by tweaking the JVM in some way (changing sizes, changing collectors, disabling features), when in fact what we more likely really need to do is find and resolve whatever is stressing things, whether it's something creating and using (and holding memory) so that it can't be GCed, or whatever. So again, good thoughts shared from others so far. I'll look forward to hearing what you find, Dale. /charlie From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf Of MrBuzzy Sent: Tuesday, August 24, 2010 11:49 AM To: cfaussie@googlegroups.com Cc: <cfaussie@googlegroups.com> Subject: Re: [cfaussie] Bad Error Something is memory hungry. Can you increase the memory thresholds in the jvm.config file? If the problem continues to occur, even after bumping up the thresholds a few times, then you have request(s) that are using lots of memory and/or not cleaning up properly. Monitor your memory usage and garbage collection via FusionReactor or something similar. Try to isolate the problem and start a code review ;) Paging Dr Arehart, you're needed in theatre. Sent from my iPhone On 25/08/2010, at 1:25 AM, "Dale Fraser" <d...@fraser.id.au> wrote: Anyone explain what can be done about this or the possible causes struct Cause struct Message GC overhead limit exceeded StackTrace java.lang.OutOfMemoryError: GC overhead limit exceeded TagContext array [empty] Type java.lang.OutOfMemoryError Detail The cause of this exception was that: java.lang.OutOfMemoryError: GC overhead limit exceeded. Message An exception occurred when performing document processing. Regards Dale Fraser http://dale.fraser.id.au http://cfmldocs.com <http://cfmldocs.com/> http://learncf.com http://flexcf.com -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
