Skip to Main Content

Java SE (Java Platform, Standard Edition)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Can't install JDK 9 because “Another Java installation is in progress”

Clancy MerrickJun 29 2017 — edited Jul 21 2017

I have been using JDK 9 on Windows 10 x64 for a while but when I went to install a recent early release (b174), I first uninstalled the previous version (as usual) and then ran the new installer.

It fails with a message box saying "Another Java installation is in progress. You must complete that installation before you can run this installer".

It seems there are some artifacts around causing the problem but only for JDK 9 as I can uninstall & reinstall JDK 8 without any issues. Also, the same problem occurs if I try to run the installers for any prior JDK 9 releases as well (even though they worked before).

Searches have suggested various options like using a Microsoft MSI clean-up tool and registry hacks but nothing helped.

Then a colleague was able to "unpack" the JDK installer on their machine and provide me with the MSI which installs perfectly.  So now I have JDK 9 b174 installed but I get the exact same original problem when I go to install b175.

As mentioned, JDK 8 early releases are NOT affected and continue to work correctly.

Is there some change in the JDK 9 installer that could be causing this problem? How can I fix it permanently so I can just use the installer instead of having to get someone else to extract the MSI for me for each new release?

Cheers,

Clancy

Comments

Dude!
Answer

No, "x" does not stand for delete, nor does "wx" mean modify.

Directories normally have execute permission in order to set a directory as a working directory, i.e. to "cd" into it. Setting write permissions (w) but no read (r) on a directory creates a dropbox, where regular users can create, modify and delete files restricted by owner and group permissions, but cannot list directory content.

Base permissions for files are 0666 and 0777 for directories. You also have to consider the umask, which is 0022 for root and 0002 for regular users. Hence the default permissions are 0644 for files and 0755 for directories created by root, and 0664 and 0775 respectively for regular users.

Setting file or directory permissions to 736 (owner/group/all) does not make sense and will give every user read and write access to files, including modify and delete. Setting file or directory permissions to 736 (owner/group/other) does not make sense and will give every user full access who is not owner or matched by group. If you require a more granulated access to files or directories, you need to setup ACL. Please check the man page for setfacl(1).

Marked as Answer by happy10319 · Sep 27 2020
Dude!

I had some doubt and did a few tests. So I wish to correct my previous post:

The permissions are owner, group and other.

However, other permissions apply to everyone unless matched by owner or group.

pastedImage_1.png

For example:

# mkdir box

# chown dude:oinstall box

# chmod 737 box

# ls -ld box

drwx**-wx**rwx. 1 dude oinstall 0 Jun 12 18:13 box

# id oracle

uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall), etc....

# id toby

uid=54324(toby) gid=54335(toby) groups=54335(toby)

As we can see below group privileges take precedence:

[oracle@localhost ~]$ cd /box

[oracle@localhost box]$ ls

ls: cannot open directory .: Permission denied

[toby@localhost ~]$ cd /box

[toby@localhost box]$ ls

[toby@localhost box]$

Double-check:

# usermod -a -G oinstall toby

# id toby

uid=54324(toby) gid=54335(toby) groups=54335(tobi),54321(oinstall)

[toby@localhost /]$ cd /box

[toby@localhost box]$ ls

ls: cannot open directory .: Permission denied

OS OL 7.6, Filesystem BTRFS.

1 - 2

Post Details

Added on Jun 29 2017
16 comments
23,812 views