As an update the server still seems to be humming along crash-free going on
3 weeks now and more importantly has cleared the christmas break hurdle.
Thanks to everyone who helped with their advice and now I have a better
understanding of what is going on in the JVM and permgen and hopefully
Willino and I were just talking about it yesterday and no problems for a
week. Thats a pretty positive sign. We have decided to not declare
victory until after the christmas break, particularly since we won't be
monitoring it as closely as during normal work times, which coincidentally
is when
On first look, I think you really need to go up on your max memory. On our
servers, which are still on 32bit windows, we have min setting of 512MB and
Max of 1182MB.
# Arguments to VM
java.args=-server -Xmx512m
# Arguments to VM
java.args=-server -Xmx1182m
Having said that, like Charlie says
Fortunately (weird I know) we just had the server crash again this
afternoon. It at least gave me an excuse to throw some new arguments into
the jvm.config file to restart the cf service
We went with suggestions from everybody and one from a ugtv webcast with
Carl Meyer that I've been watching
I would go ahead and make the perm gen 256 or 300MB
I would be surprised if they are throwing the hibernate objects into the
perm gen, but it sounds like that may be the case. Can you track the
perm gen usage before that app loads in and then after to see if it
increases when the hibernate
Like John said, try increasing perm size. I see you are not limited by 32
bit system to you can allocated more than 2gb memory of jvm memory as well.
Not sure what you have right now.
Also, have you considered FusionReactor or SeeFusion monitoring tool. Its
amazing how much these tools help you
Actually if you can, please post your full jvm.config file. I'm
wondering if maybe the heap is filling up then throwing things into the
perm space.
John
ma...@fusionlink.com
On 12/6/11 10:09 PM, Cheyenne Throckmorton wrote:
One of our CF servers keeps needing to have the CF service
On top of all that's been said, I'd add this:
Yes, it's likely that you simply need to increase the maxpermsize. Sometimes
just another 100-300 can be enough to solve the problem.
But you also want to make sure that this is really the *first* error that
puts CF into a bad state. It could be that
You guys rock with all kinds of answers, I'll definitely be trying them out
tomorrow when I have a better brain and before whirly. Below is my
JVM.config file.
Also for others maybe following the thread I found this 1 of 4 article by
Charlie helpful, but then for Charlie I was trying to find the
