Thanks Dave, I'm at home right now and will give it a whirl when I get in tomorrow.
I noted today that my jvm.config file says: java.home=C:/CFusionMX/runtime/jre and that I have JVM: 1.4.2-b28 in the C:\CFusionMX\runtime\jre folder so right there we have the JVM I am using (originally installed version) and the line that directs CF which JVM to use. I guess the thing to do is check and make sure that the java.args line reads: java.args=-server -Xmx512M as indicated in the Adobe TN you suggested. Finally, thanks for your help and one last question. Can I update the JVM that I originally installed as part of the CF installation? That is the one in the C:\CFusionMX\runtime\jre folder?? The 1.4.2 JVM is now up to _12 I think and it seems that it would make sense to update as far as possible within the 1.4 family. Thanks, Jerry >On 9/26/06, Gerald Weir <[EMAIL PROTECTED]> wrote: > >Hi Jerry. The other Dave this time! ;) > >Here's the story. In the /bin directory of your ColdFusion >installation (I don't use the standalone version of CF as you do, but >I believe it's still the same), there is a file named jvm.config. If >you crack open that file, you'll likely see a line that looks like >this: > >java.home=C:/j2sdk1.4.2_09 > >The jvm.config file is a bunch of configuration settings that the >underlying Java engine reads when it is starting up that sets things >like how much memory the JVM should use, class paths where certain >libraries are located, etc. The "java.home" line is a specific >directive that the engine reads when you start it up that says "use >the JVM at the location noted after the equal sign." You can have 100 >different Java installations on your machine, but this is the line >that matters. > >Do not use the CF Administrator to edit your jvm.config file. In fact, >even Adobe recommends that you don't do so either. Here's why. The >version first switch in the "java.args" line should say -server so >that the JVM starts in server mode as opposed to client mode (only >Java IDEs like Eclipse should really use -client mode). So, a sample >line might read: > >java.args=-server -Xmx128M -Xms128m -Dsun.io.useCanonCaches=false > >See how the -server switch is first? The CF Administrator in >standalone mode doesn't necessarily put that directive first when it >re-writes the file under the hood, and that will definitely cause CF >not to start (which is what you might have experienced). Here's a link >to a TechNote that outlines this issue further. It notes that it's for >the J2EE version of CFMX, but it happens in the standalone version as >well: > >http://www.adobe.com/go/tn_19094 > >So the bottom line is to make sure that your java.home directive >points to the corrent 1.4.2 JVM. Also, note the other Dave's comment >about a recent Windows hotfix that prevents enough JVM memory from >being consumed. This is why I'm glad I work in a Linux environment! > >Hope this helps? > >Regards, >Dave. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:254336 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
