Please find the latest update here: https://community.atlassian.com/t5/Agile-articles/Java-11-OpenJDK-support-update-for-Server-and-Data-Center/ba-p/967836#M392

Not sure if my other conversation about openJDK would be of interest to anyone.   Here is the link: https://community.atlassian.com/t5/Confluence-questions/OpenJDK-support-plans/qaq-p/784851?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic#U787433

absolutely smorri1967, we really need support for openJDK more than ever before.. but lets be real, the responsetime atlassian has on even petite changes to their own software (being more than a decade), we will all be retired by the time they even consider basing on another java..

does someone has any suggestions or knowhow, to get around the oracle-jdk issue? i tried openjdk for some time, that was not very stable.. and i +dont +(as you might read) rely much on atlassian to provide anything usable..

Oracle is changing (or changed) their Oracle JDK support structure.  We need to buy Oracle JDK licenses (not just the support contract) from Oracle JDK 1.8 onwards.  This is going to make Atlassian product deployment using VMs very costly since Oracle doesn’t recognize VMWare VM technology and need to pay for all the physical cores on the ESXi servers.

Important news for Redhat users: Redhat is going to stop offering Oracle Java via RPM in november 2018 and recommends switching to OpenJDK: https://access.redhat.com/articles/3322051.

So this is becoming a cost issue as well, as we'll have to pay for Oracle licences on a per server basis. Please start supporting OpenJDK soon - for all Atalassian procucts (we are using Confluence, Jira, FishEye, Bamboo)

JIRA isn't open source, but you get to see the source code for all licenses from $10 up. 

The supported platforms at https://confluence.atlassian.com/display/AdminJIRAServer072/Supported+platforms just say Linux/Solaris, no mention of freebsd. The heapspace with a 32 bit jvm is too small to do anything useful I agree. But the problem of the 64 bit jvm core dumping would seem to be 

Linux administration is not lightweight and agile like it was 10 years ago. It is not the best choice for a minimalist infrastructure. Any of the BSD flavors facilitate simplified infrastructure. It's easy to tell if you have to stand up a Linux box just to run the JIRA portion of Atlassian.

OpenJDK support makes a big difference in deployment value at lean and agile sites.

If I'm not mistaken, open JDK is open source whereas oracle JDK is not. Also, if I'm not mistaken JIRA is open source, or at least embraces the open source mentality. If both things are true, requiring the use of a closed source JDK seems incongruous. It would be very nice to see these two match up so that we don;t have to use tools that are encumbered by closed source foundations like Oracle's JDK.

If I'm wrong on any point, feel free to correct me.

All of us running jira on freebsd are forced to compile/install oracle-jdk, which depends on the linux compatible kernel module, that is only available in 32bit flavors - hence the jvm becomes 32bit - hence very low (2G) heapspace for jira.. i tried using openjdk_64bit (that is native to the 64bit OS), but the JVM instance coredumped spontanously, and the atlas-supportstaff told me that openjdk is not supported, only oracle-jdk is currently supported. This makes it impossible to host a sober jira instance on a sober operatingsystem like freebsd..

i suppose (based on experience with other development requests in the atlassian support-void) that this issue will be discarded in the year 2025 (10 years from date), meanwhile hundreds of paying customers only way to get this into effect, is an advisory to tell and vote for this particular issue, still ending up in utter nothingness..

but in naive hopes that my experience is not the trend, i've just voted for this issue. Please investigate and develop