Subscribe
Accepted Solution

OCI 7.0.2 Java UI and Java version issues

Hi,

 

some OCI 7.0.2 users are notifyng me that they're not be able to run Java UI from the "coffee cup" link on the OCI web portal in a lot of cases.

I know that Java 7 is a prerequisite but installing ONLY Java up to 7.21 it works but with newer versions up to 7.75 and 8.x the Java UI does not start at all.

 

Once clicked the button some seconds of wait and then nothing happen and in the task manager there's an appended java process.

 

This customer report me that they've some domain policies that automatically update their Java runtime versione so they cannot use the OCI Java UI.

Is there a way to let coexist older versions and the new Java one? 

Assuming they're forced to use the last one (i.e. 8) are there some tricks?

 

Regards,

Re: OCI 7.0.2 Java UI and Java version issues

Hey Giacomo,

 

There is a server-side patch to OCI 7.0.2 that allows co-existance with Java 7/71-72-75 and 8u23-8u31 on the client side. Do you have that patch installed?

Re: OCI 7.0.2 Java UI and Java version issues

Uh! I didn't know it! But also NetApp guys here did not know it :-)

 

I will get from support.netapp.com download pages...

 

Thanks!

 

 

 

Re: OCI 7.0.2 Java UI and Java version issues

Where's is this patch?

 

The last available is for 7.0.1 only (read in the notes)06-02-2015 17-14-55.jpg

Re: OCI 7.0.2 Java UI and Java version issues

Here's a workaround doc I wrote for my company for java compatability issues. You can have an older java version installed simultaneously with the "current" release and then use a windows shortcut to invoke that java directly against the server. The coffe cup UI will not work, but a deskop shortcut is actually more convenient anyway. Smiley Wink

Re: OCI 7.0.2 Java UI and Java version issues

Thanks.

Now I've tagged as a solution your answer but if it fails I will untag it Smiley Very Happy

Re: OCI 7.0.2 Java UI and Java version issues

We don't have individual patches available on support.netapp.com - it can be obtained via a support case

Re: OCI 7.0.2 Java UI and Java version issues

If my boss can follow it, you should be ok. 

Re: OCI 7.0.2 Java UI and Java version issues

ok so i have a windows 8.1 desktop with Java 7 build 60 64 bit installed

been battling this issue described in the article here and have tried the workarounds but no luck - not the exact same error but getting a different one:

Exception

com.sun.deploy.net.FailedDownloadException: Unable to load resource: https://servername/client/app/http-client.jnlp
 at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
 at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)
 at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
 at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
 at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)
 at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
 at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
 at com.sun.javaws.Launcher.launch(Unknown Source)
 at com.sun.javaws.Main.launchApp(Unknown Source)
 at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
 at com.sun.javaws.Main.access$000(Unknown Source)
 at com.sun.javaws.Main$1.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

 

wrapped exception:

javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
 at sun.security.ssl.Alerts.getSSLException(Unknown Source)
 at sun.security.ssl.Alerts.getSSLException(Unknown Source)
 at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
 at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
 at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
 at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
 at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
 at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
 at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
 at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
 at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)
 at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
 at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
 at com.sun.deploy.net.BasicHttpRequest.doGetRequest(Unknown Source)
 at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
 at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)
 at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
 at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)
 at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)
 at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
 at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
 at com.sun.javaws.Launcher.launch(Unknown Source)
 at com.sun.javaws.Main.launchApp(Unknown Source)
 at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
 at com.sun.javaws.Main.access$000(Unknown Source)
 at com.sun.javaws.Main$1.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

 

I would assume with all the vulnerabilities being shown for older java versions and MS activex blocking that OCI will be forced to upgrade to a newer version of supportable java - is this in the works? or even get rid of java completely? :-)

i have created the shortcut listed here a few different times but its the shortcut getting this alert - any ideas?

 

Re: OCI 7.0.2 Java UI and Java version issues

Hey Pete,

What version of OCI are you running? Has the OCI client ever worked from the machine? What you are seeing is a SSL/TLS negotiation problem. Is your workstation configured with any non-default Java settings for TLS/SSL ?

If you drop to a cmd prompt, and

ping servername

Does that resolve to the right IP address?

You may also want to drill into Control Panel -> Programs -> Java. In the Java Control Panel, you may want to review the network connection settings - are you going through a proxy? Should it be?