This is more for the “filed away for my own googling later down the road”…

A funny thing happened to me the other day. I had just deployed some new code changes and since it had some application variable changes I needed to bounce ColdFusion server. Much to my dismay CF throws and error and won’t come up. OH NO!

The event viewer wasn’t much help and just said to see the applications logs and it might help you out.

I started to look around and found a log file that CF was outputting that seemed to alude to the fact that the JVM heap file didn’t have enough room to go with the setting that it had.

I then remembered that a couple of weeks ago I had done some work on that instance and played around with the JVM heap settings. I guess I never bounced CF so the settings never too affect… until now!

Well the administrator was not coming up since of course it is written in ColdFusion so I started looking around google and found this.

http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_19359&sliceId=2

Though it says that you can’t set it to higher then 1.8 gigs what it should also say is that if JVM can’t grab that FULL memory block it ain’t running at all! This server had 2 gigs on it so I set it to 1500 since all it is doing is apache and CF. I guess that windows was using more then 500 megs and so Java could’nt get the block it wanted.

I was able to edit the config file the KB mentions and off we went.

So for next time, make sure you bounce after all config changes and make sure you don’t set the JVM heap too high!

J.J.