search : rcasdorph

Comment on Amazon Corretto Support/ Java Going away by rcasdorph

Comment on Quick thoughts on structs by rcasdorph

Comment on Running ColdFusion on Corretto by rcasdorph

Comment on CFMAIL on port 587 Issues! by rcasdorph

Comment on ColdFusion (2018 release) Update 2, ColdFusion (2016 release) Update 8, and ColdFusion 11 Update 16 released by rcasdorph

Comment on ColdFusion (2018 release) Update 2, ColdFusion (2016 release) Update 8, and ColdFusion 11 Update 16 released by rcasdorph

Comment on ColdFusion (2018 release) Update 2, ColdFusion (2016 release) Update 8, and ColdFusion 11 Update 16 released by rcasdorph

Comment on ColdFusion (2018 release) Update 2, ColdFusion (2016 release) Update 8, and ColdFusion 11 Update 16 released by rcasdorph

rcasdorph Amazon Corretto Support/ Java Going away Looking for Java Answers in 2019. Is there a plan to either get CF on Java 11 or get users the new patches?  Will there be support for Corretto? The post Amazon Corretto Support/ Java Going away appeared first on ColdFusion. CF2016 Updates

rcasdorph CFMAIL on port 587 Issues! How do we make the mail run on port 587 without getting errors? The post CFMAIL on port 587 Issues! appeared first on ColdFusion. Blog,ColdFusion 2016,Question,Windows 2016 Support,cfmail,coldfusion 2016,question,windows 2016 support

Charlie Arehart James, I know you’re asking Cavan, and I had the same question at first when I saw the comment, but I think the point he or she is making was about how Amazon will be supporting Coretto for such a long time.But neither of you (nor the OP, rcasdorph) have responded to my other

Charlie Arehart rcasdorph, are you sure that the bit-level of your CF is the same as the bit-level of the JVM you got (32-bit or 64-bit)? If so, what is the line of code you used to update the jvm.config? Did you save it as a comment? Did you point to the JRE folder within the new JVM? And since

Charlie Arehart To rcasdorph, yes. Adobe is aware of the issue, and has begun addressing it (more in a moment). First, though, it's not that you won't be able to use Java 8 without paying for it: it's that you are not going to be able to get *updates* to it for free, if you use it for commercial