Update Java (or do it by accident like me!)
For each ColdFusion instance, edit jvm.config to point to the new JVM
- Default location for wsconfig is: <drive>:\ColdFusion11\<instance>\bin\jvm.config
- Point to the correct version (x86 or 64-bit) for your CF install
- 64-bit example: java.home=C:\\Program Files\\Java\\jdk1.8.0_60\\jre
- x86 example: java.home=C:\\Program Files (x86)\\Java\\jdk1.8.0_60\\jre
- NOTE: You can also do this from the CF Admin (Java and JVM settings) if you prefer
Restart CF instances
Update the Java path for Jetty (ColdFusion 11 Add-On Services)
- You only need to do this in the default (cfusion) instance
- ??<drive>:\ColdFusion11\cfusion\jetty\jetty.lax
- 64-bit example: lax.nl.current.vm=C:\\Program Files\\Java\\jdk1.8.0_60\\jre\\bin\\javaw.exe
- x86 example: jlax.nl.current.vm=C:\\Program Files (x86)\\Java\\jdk1.8.0_60\\jre\\bin\\javaw.exe
Restart ColdFusion 11 Add-On Services
One other tip… if you had special SSL certificates installed in your Java certificate store, you will need to reinstall those.
]]>
Great stuff, Michael. Thanks for sharing it. I just pointed someone here who had raised what seems the same problem in a comment on the Adobe blog post about CF11 update 6.
Thank you for sharing this.
Windows update or something else messed the PDF Services and they were unable to start.
I installed a new jre only for Add on -service and was back in business after services restart.
Hi, Mike. I hope you won’t mind me offering this here (you can remove it if you prefer), but given the subject, I thought some finding this post may be interested to find one I did on this same subject, with a lot more detail (and other causes) for why (and how to fix when) CF won’t start after applying a JVM update.
http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start