Hi guys,

Thanks for your ideas.
Sadly, I can't use the built-in server monitor because our version doesn't have 
one. And finding out which template causes the problems is quite hard because 
the applications is built upon Fusebox and Mach-II. Yes...both of them. So the 
template context is usually insanely huge and most of the time the reported 
error location is index.cfm, which is only the Mach-II controller. Annoying.

I found an entry in the logs telling me that some request exceeded the time 
limit because of tag cfloop. Some digging unearthed some hilariously bad piece 
of code, which I deep responsible. A loop over a query contains a set of new 
cfquery tags. I assume that at some point either the processing in CF or the 
database gets bored of this and breaks down. ;)

I only wonder why the whole server doesn't work anymore afterwards. From the 
error message it looks like the overly long runtime is recognized and the 
request is being aborted. So why doesn't the server recover? I can't have an 
application that is able to break the server. Any ideas what I could do about 
that? Refactoring the code is the obvious solution, but right now I don't have 
the time (and the nerves).

Till Helge

-----Ursprüngliche Nachricht-----
Von: Russ Michaels [mailto:r...@michaels.me.uk] 
Gesendet: Montag, 11. Juni 2012 17:30
An: cf-talk
Betreff: Re: CF breaks down with error 500 (GC)


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.

On Mon, Jun 11, 2012 at 4:24 PM, Edward Chanter <firew...@cc.uk.com> wrote:

>
> 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?
>
> > -----Original Message-----
> > From: Helwig, Till Helge [mailto:till.hel...@saxsys.de]
> > Sent: 11 June 2012 15:44
> > To: cf-talk
> > Subject: CF 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
> >
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > ~~~~~|
> > Order the Adobe Coldfusion Anthology now!
> > http://www.amazon.com/Adobe-Coldfusion-
> > Anthology/dp/1430272155/?tag=houseoffusion
> > Archive: http://www.houseoffusion.com/groups/cf-
> > talk/message.cfm/messageid:351534
> > Subscription: 
> > http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
> > Unsubscribe: 
> > http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
>
>
> 



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:351552
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to