ColdFusion breaks down with error 500 (GC)

Hi guys, I got another problem that I can't figure out by myself unfortunately. Somewhere inside of the huge CF application I'm in charge of an error occurs. Not the standard error you might expect but instead an error 500 that tells me Java threw an exception with the message "GC overhead limit exceeded". And afterwards the whole CF server doesn't respond to further requests. I honestly have no idea where to start with any kind of debugging. When watching `top` on the server I can see that the coldfusion process starts allocating a lot of memory up to almost 60%. I can't really image what might cause this problem as the template that has been called does little more than retrieve a lot of information from a database. Which is what most parts of the application do and they don't cause any problems... Would be great if you have any ideas for me regarding where to start digging or what might cause this problem. Till Helge

I've seen these errors before and they almost always relate to the JVM running out of memory. Does the error/cf server log give you any clues about what template is causing the error? > Hi guys, > > I got another problem that I can't figure out by myself unfortunately. > Somewhere inside of the huge CF application I'm in charge of an error occurs. > Not the standard error you might expect but instead an error 500 that tells me > Java threw an exception with the message "GC overhead limit exceeded". And > afterwards the whole CF server doesn't respond to further requests. > > I honestly have no idea where to start with any kind of debugging. When > watching `top` on the server I can see that the coldfusion process starts > allocating a lot of memory up to almost 60%. I can't really image what might > cause this problem as the template that has been called does little more than > retrieve a lot of information from a database. Which is what most parts of the > application do and they don't cause any problems... > > Would be great if you have any ideas for me regarding where to start digging ----- Excess quoted text cut - see Original Post for more -----

check the runtime logs for some hints. Also I would suggest installing FusionReactor to do some further debugging and monitor. Have you made use of the built in server monitor as this can tell you info about memory usage and what is using memory where. ----- Excess quoted text cut - see Original Post for more -----