portal entry

Simply said, you can't use any JDK > 1.7 with CF9. So no JDK 1.8 with TLS1.2 support. <a href="https://coldfusion.adobe.com/2014/11/which-jdk-is-supported-with-coldfusion-9-10-and-11/">https://coldfusion.adobe.com/2014/11/which-jdk-is-supported-with-coldfusion-9-10-and-11/</a> At your risk, there is a workaround involving some 3rd party components: <a href="https://coldfusion.adobe.com/2018/02/tls-1-2-for-coldfusion-9-and-older/">https://coldfusion.adobe.com/2018/02/tls-1-2-for-coldfusion-9-and-older/</a>

Comment by gabrieleb5037809

<p>It’s not quite that you CANNOT use Java 8 with CF9, Gabrieleb, but rather that it was never supported by Adobe. Some folks HAVE updated CF9 (or earlier) to use Java 8, and it worked for them (solved this problem), while other have indeed had problems.</p><p>Also, there could be still other explanations for Hakan’s problems. Hakan had also asked this question yesterday in a blog post of mine (and because of an unrelated technical problem I couldn’t get my reply posted until this morning). Here is what I said there, in case it may help others finding this discussion here on the CF portal:</p><p>"<em>First, it’s worth nothing that CF9 was never updated to run Java 8. Still, many have run the two, to solve such problems and it worked (some have had problems, but they could have other explanations, since changing the JVM CF uses is indeed touchy business).</em></p><p><em>Indeed, as for the blank pages, it could be that something has gone amiss in your attempt to update the jvm and its args–assuming that is indeed all you did. I have a post on several common problems doing that, and how to solve them:</em></p><p><em><a href="http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start" rel="nofollow">http://www.carehart.org/blog/client/index.cfm/2014/12/11/help_I_updated_CFs_JVM_and_it_wont_start</a></em></p><p><em>Third, yes it’s likely that the change needed to solve your tls problem was indeed the need to update the jvm. I discuss this more here:</em></p><p><em><a href="https://coldfusion.adobe.com/2019/06/error-calling-cf-via-https-solved-updating-jvm/" rel="nofollow">https://coldfusion.adobe.com/2019/06/error-calling-cf-via-https-solved-updating-jvm/</a></em></p><p><em>Or, if you just want the problem solved, I can help remotely and often quickly via my consulting. See <a href="https://www.carehart.org/consulting" rel="nofollow">https://www.carehart.org/consulting</a>.</em>"</p><p>Sorry that the last comment may seem sales-y. Again, I am quoting what I wrote on my blog. I could have just offered a link to the comment, but I thought the other two points and links worth making sure people here saw them, even if they may not be tempted to follow a link to more.</p>

Comment by Charlie Arehart

Thank you for your clarification Charlie, probably I summarized a little too much. The sense of my response was based on the assumption that nobody should install a JVM in production that is not officially supported by Adobe, because maybe it all works, but if not... my customers doesn't deserve such type of patchwork <span></span> By the way, thank you for your insightful and extremely enlighting posts!

Comment by gabrieleb5037809

Thanks for the kind regards, and indeed you are right and wise to warn people about running unsupported configurations. I try to do so as well, whenever I may mention it, but I realize that some people are determined to "solve their one problem" even at risk of causing others. As the saying goes, "you can lead a horse to water, but you can't make him drink." :-)

Comment by Charlie Arehart