Oracle is changing (or has 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 we will need to pay for all the physical cores on the ESXi servers.
I would like you to get more information on the following items
Bitbucket already has openjdk for their Bitbucket supported platforms
However both Jira and Confluence do not currently support environments that are using openJDK for the java runtime environment yet.
There are existing feature requests for each product in:
I would suggest watching each of these for updates. Should a future release of either product begin to support that Java runtime environment, I would expect these feature requests to indicate that specific version and then our documentation to be updated to reflect that.
That said, is there a reason you need to be using the Oracle JDK over the Oracle JRE? Both Jira and Confluence can simply using the Oracle JRE instead of the Oracle JDK package to run. So if you don't need to the specific features that the JDK is offering, it might not be necessary to use that package to still run Jira/Confluence in a supported environment.
The Oracle license change appears to affect all versions of Oracle Java SE according to http://www.oracle.com/technetwork/java/eol-135779.html, not just the JDK. I'm also curious how Oracle Java licensing wiill work with Atlassian products if you won't support OpenJDK for all of your products.
Thanks for your help.
Yes, Atlassian has been bundling JREs with .bin and .exe installation packages, at least for Jira. I think the same is true for Confluence as well. Whereas if you use the zip or tar.gz installation packages, I don't think these actually have a bundled JRE with them.
These JREs don't always get updated with each Jira version. For example, Jira 7.2.0 and 7.2.1 are most likely bundled with the same JRE version. I don't have any timetable for when Jira might ship that bundled JRE 11 version, however I would expect that the supported platforms information for Jira would be updated before or about the same time that such support is added. Jira does not yet support Java 9, much less this JRE 11 you mentioned. However when a major change to a supported platform is added to the product, these details tend to also be included in the release notes for Jira.
I would recommend reviewing our Atlassian Support Offerings for more background on this third question. Atlassian does not provide support for Java itself. This is much in the same way that Atlassian does not provide database administration. Jira still needs a database to operate (and java), but the implementation and support of that database is something we would expect you or your system administrator to handle. We do the best we can to support our products that run on top of these other technologies (databases, java runtime environment, operating system, etc). Obviously Atlassian does not want to put you in the situation of having to run an unsupported or end of life product in order to use our product.
To that end, I have noticed that Atlassian tends to mirror our products end of life with the end of life of these other technologies. For example, in Jira 6.4, the supported platforms listed both Java 7 and Java 8 for Jira. However beginning with Jira 7.0, only Java 8 was supported. I would expect that Atlassian would continue this kind of stepping when it comes to keeping our products in line with the underlying technologies that make them operate.
If you're running in Windows, then I suspect you would need to use JDK to generate thread dumps. The JDK includes the jstack.exe utility that would be needed to create these. At least per https://confluence.atlassian.com/adminjiraserver071/generating-a-thread-dump-802593021.html
However in Linux/Unix environments, you don't actually need the JDK to create a thread dump. Instead you can just do a kill -3 <pid> (where the pid is the process id of the java process running Jira/confluence) in order to generate a thread dump directly into the catalina.out
I wondered how the Support Tools do it, so I looked at https://bitbucket.org/atlassianlabs/atlassian-support/src/e17276b2eb315e2335b10ae270b2e8d860d1edcc/support-data.sh?at=master&fileviewer=file-view-default
It calls jstack and there is a line
echo "Error: jstack is not present in your system. Please install Java JDK"
It would be nice to use kill -3 but it just doesn't feel right somehow!
@Andy Heinzer just so I'm clear.
1. We can use the bundled JRE's with each of the installers (Jira, Confluence, BitBucket) without paying for any additional Oracle support because it is bundled by Atlassian.
2. We don't need to pre-install any Java JRE/JDK on our Rhel7 VMs.
3. Atlassian will provide version patches (that might include a JRE patch) if there is a vulnerability or defect identified, and that update can be handled by the Datacenter zero downtime maintenance process.
4. Future Atlassian major/minor releases will come with JRE updates to keep the products on a supported version of Java.
Are all of these statements correct?
I will try to clarify further:
Please understand that it takes time include updates to things like Java into our installation packages. It's not an immediate thing.
From what I am reading, you guys at Atlassian are going to have to change the way you do things.
Either you need to be prepared to move to a new Java version every 6 months, or you'll need to start using a Long Term Servicing Java version that provides 3 years of support but requires a monthly subscription for each and every installation of Java that your customers have deployed.
Going without Java updates is unacceptable, so that is not an option.
And if Atlassian starts putting the impetus of Java updates on its customers, you're going to lose customers most likely, because that would make some Atlassian too expensive to maintain.
I hope you guys are taking the Oracle Java servicing changes seriously because other businesses are already having to make significant plans, like getting off Java.
On this topic, you might be interested in the latest update regarding plans for supporting OpenJDK 11 across all Atlassian Server & Data Center products -> https://community.atlassian.com/t5/Jira-discussions/Java-11-and-OpenJDK-support-for-Atlassian-Server-amp-Data-Center/m-p/872998#M4575
Just to add a data point, I have been running Jira and Confluence on OpenJDK for years. Furthermore, I run it on FreeBSD, which hasn't been a supported platform since Jira 4.
The only noticeable issue I have is that issue search links in the body of confluence pages to jira issues twirl and time out, and that only started recently. It used to work until about 1.5 years ago or so (don't recall the versions involved). Curiously, the issue reference links in the confluence page header work just fine.
I would expect it to work since Oracle JDK and Open JDK are built from the same source tree.
ive been running various jira versions for 4 years on freebsd - not a problem in that, but when i tried combining openJDK with Jira 3 years ago it broke. Tomcat spontanously crashed.. daily.. so i went back to oracleJDK
as i read the JDK licensedeal, it means we only have to pay when/if we need additional support extending to the three years support for the to-be oracle-jdk versions. And i figure most jira installations are upgraded at least once every three years.
Ready for the monthly rollup of what happened in May for Confluence Cloud? Improved mobile login experience (& SSO) For those of you with the Confluence mobile app, we know the login experien...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events