Thanks for the good follow up info. I'll be interested in your learning
curve for figuring out JConsole.
~Brad
Original Message
Subject: Re: Debugging Out of Memory errors, SeeFusion Memory / Active
requests graph
From: Dominic Watson
Date: Thu, November 19, 2009 9:08
Subject: Re: Debugging Out of Memory errors, SeeFusion Memory / Active
requests graph
An update on this, for my own reference as well as for people googling. I
have, following various people's advice, changed the memory profile of our
application quite dramatically and I will summarize w
An update on this, for my own reference as well as for people googling. I
have, following various people's advice, changed the memory profile of our
application quite dramatically and I will summarize what I changed and the
tools I used to find the problems. I shall properly blog this later, no ti
Right, so changing Eden memory size had a slight effect on the memory useage
pattern (spikes only going up to around 80% instead of 95%), but did not
stop the crashing.
Getting to grips with JConsole has been really useful / educating. I have
been monitoring all three of our live servers overnigh
Thanks a lot Paul,
I'm getting to grips with JConsole now and looking into the Eden memory
settings. I'll be sure to blog about what I find (if its the same problem as
yours I'll simply link to your post, init).
Dominic
2009/11/16 Paul Vernon
>
> > and have reduced the troubles a great deal.
> and have reduced the troubles a great deal. However, there still seems
> to be
> an underlying problem that is causing CF to crash out with multiple
> instances of the error:
>
> "unable to create new native thread The specific sequence of files
> included
> or processed is: [xxx] "
> java.lang
6 matches
Mail list logo