-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OS X El Capitan "Java 6" dialog when loading libpljava-so-1.5.0-BETA1.bundle referencing Java 8 #96
Comments
Thanks, that eliminates one easy explanation. (Too bad, because I was kind of hoping for the easy explanation. But elimination is good.) There is no linked-in reference to a different JVM to be causing the problem. Somehow, that Java 6 dialog is appearing when PL/Java explicitly tries to load the Java 8 library named in Is there any chance of getting a careful, technical English translation of that dialog? There is not much information shown by
just before the |
Thanks for your help. The dialog message simply means that 'you need to install legacy Java SE 6 to run the Java application'. Similar to this: https://kbpdfstudio.qoppa.com/?p=2393
server.log:
|
That's an interesting line in the server log: What do the buttons on that dialog say? I wonder whether somehow your Java 8 installation did not get completely finished, and somehow OS X thinks it is not usable. I see some StackOverflow posts where it seems that a button on the dialog might take you to a download page for a current Java version. If it only goes to a Java 6 download that is no good, but if it allows a Java 8 download, maybe it is worth trying. Perhaps if the installation is done through Apple's dialog, it will then be usable, where somehow your previous installation method does not seem to satisfy the OS. Some comments point to the System Integrity Protection feature in OS X - perhaps it may have blocked some critical part of your Java installation before. Only a guess though. |
By the way, the debug messages all the way up through |
I installed jdk-8u74-macosx-x64.dmg from the official oracle site, no issues at all (run the installation and follow the steps). Never had to deal with SIP issue in OS X. In fact, I am running a web app on tomcat without any issues. Even applet I can run without any issues. All using the java 8 installed. |
All of that may be true, but it is also true that opening |
I might be inclined to give dtruss a try. You could start a psql session, |
dtrussoutput.txt |
I've tried the installation on El Capitan and it runs smoothly, I have to say that I have a bunch of jvm installed even legacy 1.6
|
Daniel, thanks for the test. Do you happen to have (I think you can check with -Chap |
Looking at that that's got some things I didn't expect.
|
no, i didn’t
test=# SELECT getsysprop('java.version'); getsysprop1.8.0_65 $ps -wwE -p 67489
bash-3.2# su - postgres hal9001:~ postgres$
|
Hmm. I wonder if you could do a -Chap |
I just installed the old java SE 6, now it works! Clearly somewhere the mac el capitan still reference this. Anyway, at least this is a work around. |
Good news! I trust you've confirmed the version PL/Java is actually using is still 8, right? I wouldn't mind looking at another |
Yup, confirmed using java 8: select getsysprop('java.version');getsysprop1.8.0_74 We probably should document this issue so that other people can save the troubleshooting we went through. Thanks for your expertly help along the way! |
I have the dtruss dump of my working installation. Having a glance at it, to me it seems that error probably was because java wasn't properly installed. Probably it needed user confirmation before authorizing java to work on his machine. I vaguely remember a similar issue when I switched to El Capitan, but I'm not 100% sure. Here you have. |
Hi, I got a fix for this: don't use
Worked on a OS X El Capitan virtual machine running in VirtualBox (ran on my MacBook Pro, so I'm not doing anything illegal)
Some query history
|
Great find, thanks! This seems about the ideal solution; just use the existing GUC to point to a different |
This was an annoying thing to troubleshoot, and the elegant solution was found by Dos Moonen.
Covered in documentation in 1.5.0-BETA2. |
(Editing this issue for context; the reporter began it on the end of a different issue #94. -Chap)
(This is OS X El Capitan, 10.11.3. After building 1.5.0-BETA1 and setting config variables as follows)
(The following popup is reported to appear, even though
pljava.libjvm_location
explicitly refers to an installation of Java 8.)(
otool
shows the following libraries coded into thepljava
bundle):(There should not be any reference to a different JVM coded in, and there is not, so that is as it should be.)
The text was updated successfully, but these errors were encountered: