Darkoshi

Oracle JDK download not working

Sat, 24 Mar 2018 07:11:28 GMT

Trying to get the Android SDK to work, so I can root my phone. It requires Java, though it doesn't tell me what version.

On the following Oracle JDK 8 page, when I click the radio button to accept the license agreement, and click any of the download links, I get the error "We're sorry, the page you requested was not found."

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

I even tried the pages for the Java 9 and Java 10 JDKs. All of the download links get the same error. I tried with different browsers. I even logged in to the site, as is sometimes required for downloading older versions of the files. What is going on? Are the links working for anyone else? Is it a temporary outage? How can the world go on, if the JDK can't be downloaded anymore? Did everyone switch over to using non-Oracle JDKs? AAAAAHHHHH.

Now I thought to search Twitter. It's not just me; other people are having the same problem:
https://twitter.com/search?q=oracle%20jdk&src=typd
Well, that's a relief, sort of. But is the world going to end?

So I decided to try downloading OpenJDK instead. Apparently that's made by Oracle too. But why does the main download page say that JDK 9 and 10 are "ready for use", while JDK 8 (Updates???) are "early access"? Eh? At least I found a working download link there.

Update, 2:21pm:
The Oracle downloads are working again now. An Oracle employee posted on this reddit thread that the temporary outage was resolved about an hour ago. That's the only semi-official notice I found about it. No mention of it on Oracle's twitter feed, even though I counted about 20 tweets directed at oracle about the problem. Based on the posts on twitter and elsewhere from people getting the 404s, the outage was from around midnight to 2pm (EDT).

comments

Java Update settings Fail

Thu, 17 Jan 2013 21:09:17 GMT

Based on an articles such as these, I've gone ahead and disabled Java in my browsers:

Java Security Fix Issued By Oracle, Feds Maintain Warning To Users

Serious Flaw in Java Software Is Found, Then Patched

How to turn off Java on your browser - and why you should do it now

As it turns out, I had a fairly old version of Java on my machine, due to having turned off updates a couple of years ago. So I updated to the Java version with the latest patches (1.7.0_11) and turned updates back on. As I had disabled Java in the browsers, I decided to have Java to check for updates on a weekly rather than daily basis.

The next day after I booting my computer, my ESET firewall notified me that Java Update Scheduler (jusched.exe) was attempting to access the internet. In order to track how often Java was checking for updates, I only gave it temporary permission and did not create a firewall rule for it yet. I also changed the Java settings to check monthly instead of weekly, to see if that would make a difference.

Yet jusched.exe still attempts to access the internet every day! I'm not even clear why jusched.exe is accessing the internet. From what I understand, it is only a scheduler, and jucheck.exe is the program which should check for updates.

In addition, the Java "Automatic Update Advanced Settings" dialog is quite odd. There isn't really a setting to control how often it checks for updates. There is only a setting to control how often you are *notified* of updates.

When you select "Weekly", it says, "Java will check every Sunday at 12:00AM and notify you within 7 days".

When you select "Monthly", it says "Java will check weekly on Sunday and notify you within 30 days".

Regardless if you select weekly or monthly, it claims that it will check weekly. Furthermore, what is the point of checking for updates but then waiting 7 or 30 days to notify you that updates are available? I would expect a program to notify me of available updates right after it has checked and found them. I want to control how often it checks for them, not how long it waits to tell me about them after it finds them.

I believe that this is why I turned off updates 2 years ago - it annoys me the settings dialog claims that it will check weekly when in fact it checks daily, and that I can't control how often it checks for updates.

This page explains how to set up your own task in Windows Task Scheduler to check for updates, rather than using the Java Update Scheduler. But each time this task runs, you'll get at least 1 popup window which you'll have to close, even when no updates are available.

I feel that one shouldn't have to go through that much trouble... I'm feeling rather disappointed by Java, which is a shame as it is currently my preferred programming language.

comments

Eclipse rebuilds when jar files change

Tue, 18 Oct 2011 00:53:22 GMT

At work, we're using Eclipse for our Java development environment.

Something I don't understand, is why Eclipse thinks it needs to recompile my projects when a jar file on the Build Path has changed.

We have jar files which get updated fairly often. The jar files are built in a separate project, and then promoted into one of the projects that I work with. It takes about 20 minutes for Eclipse to rebuild my projects from scratch, so I don't want Eclipse doing a full rebuild whenever one of the jar files is updated. I only want Eclipse to build the Java files that have changed.

Eclipse indicates that it is doing a "scoped incremental build", but in reality, it first cleans the output folders, so that it ends up doing a full rebuild of all the code.

Originally, my build path included the jar files in my workspace. I tried to avoid the problem by copying the jar files to a folder outside of my workspace, and by updating my build path to point to the files in that other folder.

This partially fixed the problem. Eclipse no longer did a full rebuild when I manually selected to build the projects. It only built the changed Java files, as I'd expect. But when I clicked to start debugging the projects, *then* Eclipse did a full rebuild after all.

I found out that there is a setting in the Preferences - "Build (if required) before launching". Presumably unselecting that option would avoid the full rebuild when I start to debug.

But my question is, why does Eclipse think that a rebuild is required, when only a jar file has changed? Is it really necessary? Shouldn't the jar file changes be automatically picked up at run-time, without recompiling the calling code?

The only thing I can think that the rebuild may accomplish, is to flag any errors which may exist due to mismatches between the calling code and the jar files. It shouldn't actually result in any changes to the compiled class files, right? Or am I mistaken?

When I've updated my workspace from the repository, there shouldn't be any mismatches between the Java modules and the jar files, so I don't see any benefit to doing a full rebuild.

I may need to find an Eclipse forum to post my question.

comments