portal entry

Glen, that's likely too complicated a set of variables to expect an answer here. Adobe traditionally asks folks who ask licensing questions to reach out to them directly. I forget which address it usually is, but if you send to <a href="mailto:cfinstal@adobe.com," rel="nofollow">cfinstal@adobe.com,</a> they will get you to the right person (yep, that's one letter L). In the meantime, I will say that I am not aware that even CF can be licensed "for a specific number of virtual cores but not all the physical cores in a cluster", at least not as I read the EULA. Perhaps there are custom licensing agreements that cover that. CF is normally licensed on a per machine basis (real or virtual) and per x cores. <a href="https://coldfusion.adobe.com/2018/01/finding-the-eula-end-user-licensing-agreement-for-your-installed-cf-version/">See the EULA</a> for more. Finally, as for the licensing of Java for use with CF, that has really not been made clear other than <a href="https://coldfusion.adobe.com/2019/01/oracle-java-support-adobe-coldfusion/">the initial post by Adobe here from 2019</a>, nor is the Java licensing mentioned in the current CF EULA. But from all I have read (there and its 60+ comments) and elsewhere, the point seems to be that as long as you are only using the Java for CF (and not other production uses), then CF users are covered and don't need to license Java. That last point would seem to address your point about "We are not specifically using Java across the rest of the cluster", but I will say that again when you try to talk about how a license related to CF covers "cores across a cluster", you are indeed getting beyond what the CF EULA covers, to talk to Adobe for that. Finally, I can say that Adobe has said (and said in the 2019 post above) that they are NOT currently supporting any Java other than Oracle's--which is why it's so important that they licensed it for us. Some people HAVE used CF with other jvm's (openjdk, coretto and more), but again it's not SUPPORTED and may be unwise to rely upon in production. HTH.

Comment by Charlie Arehart