Java Se 8 Openjdk
Filis Cianciotta
It seems possible there might have been a glitch in the mirror sync that triggered the error. For both F37 and F38 those packages both install nicely with no conflicts., and the F36 versions I can access also have no conflicts.
Ok, I see the error in that output.
Please, in the future post the text into your post since pastebin only keeps the data for a default 24 hour period and it will be gone tomorrow unless actually part of your post.
It is complaining about the java-latest-openjdk-headless package which conflicts.
Have you tried adding the options --best --allowerasing to your command line to see if an option is suggested by dnf. That looks like it is actually the same package with a different build number as is used for all the recent versions of fedora.
Uninstalling java-latest-openjdk-headless and then running dnf upgrade adds it back without the error. Hopefully that will be good enough to avoid a failure during the upgrade process to Fedora 37 or 38.
However, the "tech support" advice you got was almost certainly crap. They just wanted to get rid of you ("have you tried turning it off and on again"). Uninstalling and reinstalling will do nothing to help the situation, and if it would, reinstalling alone would be sufficient (e.g. just use `pacman -S jre7-openjdk`).
Now there are several proprietary java tools that will only run with oracle's official java (from the AUR), and sometimes only with specific versions of it. For a current project, I need to use BlackBoard Collaborate. It took a while to troubleshoot, but that only runs with oracle's jre8 from the aur (none of the openjdk packages worked, no other version of oracle's jre worked).
"Update 161" means "latest oracle java version", and most likely means that Trilby is right about the tech support. I assume Java8 will do, but is presently not used (7 is the configured default) - see the link I posted on how to try Java8 w/ the program.
I want to start toying around with java (eventually getting to the point where I can write basic little programs for android or web), but I've managed to have java messed up on my computer (from past experiments).
I'm not sure which version of java I have, and would like to know if there is a command to see the version of java that is installed and active. Also, which version works best? All this on 32bit Ubuntu 12.04
EDIT:
Ok, so it seems like I have both openjdk 6 and 7, with openjdk 7 in use. I want to use openjdk 7, so how do I uninstall openjdk 6? Is just via USC good enough or is there a command that should be run?
However, whichever method you use, you may want to check first to see what depends on these packages--you might have software installed that specifically needs version 6. (Probably not, but possibly.)
If you want to be able to continue using Java content online in your web browser (this is not the same thing as JavaScript), then before you remove any icedtea-6- or openjdk-6- packages (except perhaps openjdk-6-jdk), you should make sure you have icedtea-7- packages installed corresponding to whatever icedtea-6- packages are installed.
I highly suggest using Java 7, but the updates will try to install Java 6 too. That is OK. But your default should still come up as 7. Everything I have thrown at it works as long as your video card drivers work.
Since JRE_WANT_VENDOR is 'Oracle Corporation' and most third party vendors put their own name into 'java.vendor' it makes sense to use 'java.specification.vendor' since this is 'Oracle Corporation' for all supported OpenJDKs (I tested this for Azul and Adopt, therefore I assume this valid for others, too)
But supporting Open JDK is on the way starting from DB Connect 3.1.4 which is the next release. This schedule can change without any notice. If this is not supported even with DB Connect 3.1.4, please submit a Splunk support case and request the progress of DBX-2531.
This is pretty confusing. I expected the Java Development Kit to come with the Java Compiler. At least, I expected to be able to install javac easily. Note that note even software.opensuse.org is of great help here.
No need to be rude, @pbiel is absolutely right that most packages that have a -devel suffix are meant for compiling the package itself (or to use the headers to compile other software that uses it as a library). Maybe Python was an odd example as it is an interpreted language, but the point still holds, python-devel is to compile the Python interpreter, not to develop Python programs.
In the Java world a JDK always has included javac. It literally means java development kit. If you are only interested in running Java programs, there is the JRE (java runtime environment) for that.
It turns out that I needed only openjdk 16 to run what I wanted to, and having other versions of java are kinda pointless. My main issue is that programs default to version 8 and I can't seem to fix it.
The problem is that openJDK does not print 'java version' but 'openJDK version' and the provided script does not grep for that. I assume openJDK is compatible? After I fixed the issue it seemed to work just fine.
The below is some scratch code (with some diagnostic lines left in, sorry) that fixes the issue on my machine -all I've done is truncate the search string, but I'm sure you can produce a neater and safer fix - its just to show the priniple:
To make it at least try to start the system with OpenJDK, you will need to amend the scripts in /bin, such that they look in the right place and perform different checks for Java. setenv.sh and start-jira.sh are the main ones from memory. That will get Tomcat running, but once it gets to Jira, all bets are off - it will probably appear to work for the basics, and may even work fine overall, but most add-ons will fail.
Has that fact changed since you wrote that? Our firm is on the path towards OpenJDK and I have not come across any definitive news of Atlassian support for that. I trust your insight so I am asking you first.
Thank you! I did manage to install openJDK, and it kindly updated all the update-alternatives for me. (Thank goodness!) I kept the IBM one on there in case something might want to use that java some day (and can have its java_home set!)
cimg/openjdk is a Docker image created by CircleCI with continuous integration builds in mind.Each tag contains a version of OpenJDK, the Java Development Kit and any binaries and tools that are required for builds to complete successfully in a CircleCI environment.
In the above example, the CircleCI OpenJDK Docker image is used for the primary container.More specifically, the tag 21.0.2 is used meaning the version of OpenJDK will be v21.0.2.You can now use OpenJDK within the steps for this job.
- The version of OpenJDK to use.This can be a full SemVer point release (such as 11.0.2) or just the minor release (such as 11.0).If you use the minor release tag, it will automatically point to future patch updates as they are released by AdoptOpenJDK & Oracle.For example, the tag 11.0 points to OpenJDK v11.0.5 now, but when the next release comes out, it will point to OpenJDK v11.0.6.
The browsers variant is the same OpenJDK image but with Node.js, Selenium, and browser dependencies pre-installed via apt.The browsers variant can be used by appending -browser to the end of an existing cimg/openjdk tag.The browsers variant is designed to work in conjunction with the CircleCI Browser Tools orb.You can use the orb to install a version of Google Chrome and/or Firefox into your build. The image contains all of the supporting tools needed to use both the browser and its driver.
The Java Runtime Environment (JRE) is required to run Java programs. Nowadays there are many JRE packages available from a variety of projects and companies, but the two most popular on Ubuntu are OpenJDK and Oracle HotSpot. Using one package over the other should not create any functional difference in most applications; however, some prefer OpenJDK over Oracle HotSpot as the former does not contain closed-source components, has a much clearer licensing and support policy, and is maintained as part of the Ubuntu archive, with easier installation and upgrades.
With new versions of Java released every 6 months, there are multiple versions available for use. Nowadays, Java 11 is the current Long Term Support (LTS) version, but Java 8 is still widely used. Moreover, the non LTS versions of Java are bringing a steady stream of innovation into the language, and also see some adoption.
Ubuntu offers the default-jre package, which is regularly updated to ship the latest version of the current OpenJDK JRE in Long Term Support (LTS). The default-jre is an excellent choice for most situations, thanks to the outstanding track of backwards compatibility of the Java Virtual Machine.
(Alternatively, you may opt to use a specific Java version, using for example the openjdk-11-jre package; as updates are released for that version of the Java Virtual Machine, that packages will be updated, allowing you to stick to the latest and greatest update of one specific version of the Java language.)
Experience shows that JVM crashes of this kind are almost always fixed by upgrading to the latest JVM version, so I would recommend you try that (and make sure to pay attention to Oracle's licensing changes)
For the out of memory case, you should see one or more java.lang.OutOfMemory exceptions in the application logs. Alternatively, if you see no out of memory exceptions logged, you could double confirm that memory headroom is not the root cause by setting the JVM to heap dump on out of memory and making sure there is no heap dump created.
If you do find a fatal error log, you will need to try and match the symptoms in the log with known JDK bugs. The fix for out of memory would be to increase Xmx to allow additional operating headroom.
Also i have deployed the application in cloud foundry and cloud foundry also doesn't show the crash reason as out of memory as it should show in case of OOM. But as heap dump is generated, it is giving an indication that OOM is happening but doesn't look like heap.
d3342ee215