We've now observed CFMX Admin corrupt jvm.config in two different ways, preventing CFMX from running. (CFMX 7 and higher, on Solaris 9)
1) Editing JVM min. and max. sizes in CFMX Admin can corrupt jvm.config, preventing the required restart. We've also seen the jvm.bak backup get corrupted. Manually editing jvm.config works fine. 2) Entering a path in "ColdFusion Class Path" in the Java and JVM section of CFMX Admin. When we pressed Submit, CFMX said it would have to be restarted to accept the change. We postponed the restart to a less busy time. However, within 1.5 hr. CFMX apparently read the change, attempted to write it to jvm.config, corrupted jvm.config, saved a corrupted version in jvm.bak, and crashed. Thoughts: - manually backup jvm.config before making any changes to the Java and JVM section of CFMX Admin. - don't "pre-position" any changes. If CFMX needs a restart, do it then to confirm it'll be accepted. - edit jvm.config by hand to keep CFMX Admin from touching it! Chris Norloff ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:236535 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
