portal entry

I will comment that using Java 11 on ColdFusion 2016 caused an error with CFHTTP connecting to Google's Captcha Service. I would get a "Connection Failure: Status code unavailable." error. I reverted back to the previously used JDK of 1.8.0_161 and it started working again. The version I am referring to is 11.0.2 found @ <a href="https://www.adobe.com/support/coldfusion/downloads.html" rel="nofollow">https://www.adobe.com/support/coldfusion/downloads.html</a>.

Comment by Giancarlo Gomez

Giancarlo, that's a little off-topic, as this was about CF2018 and its latest installer having Java 11 built-in, but perhaps you're fearing your problem could affect those on CF2018 who go to Java 11. I'll say I've not heard of that issue before, but again it's early days for use of CF with Java 11. Even so, here are a couple of other things to consider, before we may presume it's inherently a bug. First, try deleting the underlying cfclass file of the template doing that cfhttp. It may be calling libraries in a way it would not, if the code was recompiled by CF for Java 11. When folks move CF from using on major Java version to another, I recommend they stop CF and clear out that cfusion/WEB-INF/cfclasses folder (or rename it, and CF will create it anew on restarting). Second, I presume you just applied one of those latest updates from Feb or Mar (8, 9, or 10) which added Java 11 support to CF2016. You don't say. You can't use Java 11 with CF2016 if you're still on update 7, that does NOT formally support Java 11. Third and finally, do make sure also that you had no errors in applying your last update, whichever of those 3 it may have been. For more on how to do that, see my post, <a href="https://coldfusion.adobe.com/2019/03/problems-applying-cf-update-check-first/">https://coldfusion.adobe.com/2019/03/problems-applying-cf-update-check-first/</a>. Even if you "don't plan to go to Java 11 again anytime soon because of the problems", you can (and should) still check out that last point. But if you can try the first one (and confirm the second), I'd be interested to hear if it may fix things for you.

Comment by Charlie Arehart

<p>Hey Charlie,</p><p>Sorry for the late reply and sorry for posting that here as I jumped the gun on the Java 11 title in the heading and my 2016 issue. Well as we discussed in DC, it appears the issue was caused by a flag I had in my jvm.config. The flag causing the issue was this one “-Dcom.sun.net.ssl.enableECC=false”, once I removed it, the cfhttp connection was able to complete the SSL handshake and work <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f642.png" alt="??" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>

Comment by Giancarlo Gomez

<p>Thanks for the update, GC.</p><p>Glad you got it working, and hope the info you shared may help others.</p>

Comment by Charlie Arehart