Fedora: Updating Java (JRE) for a Non-Sudo User with a Custom Installation Path

If you’ve ever managed a Fedora Linux server, you’ll likely recognize the situation we’re about to discuss. Suppose you’ve successfully installed the latest Java Runtime Environment (JRE) using your admin account, but when switching to another user, you’re still stuck with the older Java version. I’ve been there, and believe me, it can get pretty frustrating.

Here’s the scenario: you’re logged in as a privileged user named adm who can easily update software using sudo commands. When you run which java, your installation points to a typical default path, such as /usr/bin/java. Everything looks neat and updated.

But here’s the catch: Another user on your system, let’s call them pso, doesn’t have sudo privileges. When pso checks their Java installation by executing which java, they see Java installed in a completely separate custom installation path, like /u01/jre/bin/java. Importantly, this path still points to an outdated Java version.

This mismatch leaves you with a significant challenge: how do you effectively update Java for a non-sudo user who has their installation in a custom directory? Don’t worry—there are practical solutions to overcome this problem, even without granting sudo privileges.

Understanding Your Current Java Setup on Fedora

Let’s start by taking a clear look at the existing Java installations. From your admin account (adm), check the installed Java path by typing:

which java

The result is straightforward:

/usr/bin/java

Then, switching to the pso user account (without sudo privileges), checking Java installation again gives you:

/u01/jre/bin/java

Clearly, you have two different Java installations in two different locations. Just updating Java with the admin account using sudo rpm -ivh jdk-xxxx.rpm will only update the Java installation in default locations, leaving the custom path unchanged.

Even simply setting JAVA_HOME as an environment variable to the newer location doesn’t automatically update the Java command path for pso. Let’s say you tried that and ran java -version again as the pso user. You’d see your older Java version stubbornly appearing, indicating your command line still points to the older installation.

So what’s causing this?

Basically, your non-sudo user’s shell environment configuration or PATH variables are still referring to the previous Java installation. Updating Java at the default location /usr/bin/java doesn’t change the custom user-specific paths like /u01/jre/bin/java automatically.

Practical Ways to Update Java for Non-sudo Users on Fedora

Thankfully, solving this isn’t too complicated once you understand what’s happening. I’ll walk you through three practical methods to update Java effectively for non-sudo Fedora users.

Method 1: Change Ownership and Permissions on Custom Java Path

This approach involves changing ownership and permissions for the Java installation directory (/u01/jre/bin/java) to allow the non-sudo user to update or replace Java binaries manually.

Firstly, log in as adm and execute:

sudo chown -R pso:pso /u01/jre
sudo chmod -R 755 /u01/jre

Then, switch users to pso and directly replace the old Java files or binaries with the downloaded newer Java JRE files. After replacing the binaries, verify the updated Java version:

/u01/jre/bin/java -version

You should now see the updated Java installed exactly at your custom location.

Method 2: Installing Java Directly to Custom Path for Non-Sudo User

Suppose you prefer not to alter existing permissions globally. You can directly install the new Java version to your custom path as the non-sudo user. Here’s how you do it:

Download the latest Java Runtime Environment (JRE) tar file from its official Oracle Java archive or another trusted repository (Oracle JRE website).
Place the file in your custom directory (for example, /home/pso/java_install).
Extract it using:
```
tar -xzvf jre-xx.tar.gz -C /u01/jre --strip-components=1
```
This command extracts files directly into the custom JRE directory, neatly replacing the older version.

Once extracted, test the result immediately from pso‘s account with:

/u01/jre/bin/java -version

You’ll see the new Java version successfully installed, all without ever using sudo.

Method 3: Adjust User Configuration to Look at the Updated Java Version

Sometimes, the Java installation actually went fine, but your command-line environment and PATH variables are pointing elsewhere. To fix this easily, adjust the following inside your .bashrc or .profile in the user’s home directory:

export JAVA_HOME=/u01/jre
export PATH=$JAVA_HOME/bin:$PATH

Then run:

source ~/.bashrc

Check again with:

java -version

Now your system seamlessly picks up the correct Java installation.

Which Method Works Best for You?

Each method above tackles this updating challenge from a different angle:

Method 1 suits scenarios where the admin user agrees to alter permissions on the specific custom install path for easy updates in the future.
Method 2 fits if you prefer downloading and installing Java manually as a non-sudo user independently, without waiting for admin permissions.
Method 3 works better if the Java version is already updated at your custom installation path but you’re still facing environment variable or PATH issues pointing Java commands elsewhere.

Feel free to combine these methods as they’re not mutually exclusive. Whichever route you choose, always double-check Java version updates afterward for confirmation.

Properly managing software updates without sudo privileges helps keep your environment flexible yet secure. Java applications often require updated Java versions for compatibility with frameworks like Spring, Java SE APIs, or even Apache Maven, helping maintain reliable uptime and performance.

For handling similar situations with JavaScript runtimes like Node, check out my other detailed guide on JavaScript management and troubleshooting.

Keeping your Java versions current isn’t just about security and updates; it’s about ensuring great performance, compatibility, and reliability for applications and users alike. Have you struggled updating Java without admin rights before? What are your favorite tips or shortcuts to manage this issue efficiently? Let me know your thoughts below!