If you missed the pre-registration for NetApp MS Azure AD B2C, the new login prompt will offer the option to register. Please note that access to your NetApp data may take up to 1 hour.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Active IQ Unified Manager Discussions

OCI 7.0.2 Java UI and Java version issues

gmilazzoitag

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. 😎 are there some tricks?

 

Regards,

1 ACCEPTED SOLUTION

tflammger

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. 😉

View solution in original post

39 REPLIES 39

AmrShans

Hello everyone,

We have got OCI 7.1 but I am still getting this error with Java 8 u 60. The Java client initially worked on my Win 7 machine but not anymore, however, it works from the Server.

Shot 3.jpg

ostiguy

OCI 7.1.what?

 

OCI 7.1.0 ships with some default ciphers enabled which have been rendered unsupported by default in recent Java releases, so if you are running 7.1.0, changing the cipher list and restarting the "SANscreen Server" service should resolve it permanently.

 

 

When you see screenshots like that, clicking the details button, and harvesting the contents of the next window can be useful.

 

OCI client log file is sanscreen-client.log , which lives in

 

%userprofile%

 

on Windows. On WIndows 7, that defaults to

 

c:\users\%username%\

 

Having that can also be helpful

 

Matt

AmrShans

@ostiguy wrote:

OCI 7.1.what?

 

OCI 7.1.0 ships with some default ciphers enabled which have been rendered unsupported by default in recent Java releases, so if you are running 7.1.0, changing the cipher list and restarting the "SANscreen Server" service should resolve it permanently.

 

 

When you see screenshots like that, clicking the details button, and harvesting the contents of the next window can be useful.

 

OCI client log file is sanscreen-client.log , which lives in

 

%userprofile%

 

on Windows. On WIndows 7, that defaults to

 

c:\users\%username%\

 

Having that can also be helpful

 

Matt


Thanks a lot Matt.

It is OCI 7.1.0 Build 228.

After clicking details button on the error pop up I got the follwoing:

 

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)

 

 

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.getInputStream0(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.access$200(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessController.doPrivilegedWithCombiner(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)

 

while the most recent entry in the OCI client log file is:

 

************************************
2015-08-28 08:22:02,259 ERROR [pool-1-thread-106] com.onaro.sanscreen.client.ejb.SessionsManager (SessionsManager.java:454) -
*** Exception occurred on server ***
*** Reason : javax.ejb.EJBAccessException: Invalid User
*** Possible cause : Server Down
*** Troubleshooting : Restart Server
*** Server Method : public abstract com.onaro.sanscreen.server.interfaces.data.update.UpdateTimes com.onaro.sanscreen.server.interfaces.remote.UpdateTimeRemote.getUpdateTimes()
*** Parameters : ***HIDDEN***
************************************

 

Thanks a lot,

Ammar

 

ostiguy

Yep, that is the ciphers thing - "handshake" messages are almost always TLS/SSL negotiation failures

 

RDP to the OCI server

 

C:\Program Files\SANscreen\jboss\server\onaro\deploy\jbossweb.sar

 

Make a backup of server.xml to your My Documents folder

 

Line 45 should start with

 

ciphers =

 

change it to

 

ciphers = "TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA"

 

save the file

 

Restart the "SANscreen Server" service.

 

You should be good to go

AmrShans

Thanks a lot Matt for the prompt responses. I have edited server.xml with the details provided however I still get the error. Initially I wasn't getting any response but after a while the error returned. Are there any other issues that could cause this?

 

Regards,

 

Ammar

 

ostiguy

Hmm,

 

Can you post a current sanscreen-client.log?

 

Matt

AmrShans

 


@ostiguy wrote:

Hmm,

 

Can you post a current sanscreen-client.log?

 

Matt


Sure. See attached. Thanks.

ostiguy

Curious - none of the events are recent.

 

General Java things:

Add/Remove Programs in Control Panel - if you have multiple Java runtime environments installed, try removing the old ones - sometimes despite Java prompting you to install new versions, the old ones are kept around

Java icon in Control Panel - try clearing out the cache of applets/etc.

 

Try both, and then reattempt launch the OCI client.

justin_smith
Negative. We haven't worked with support yet to get it.

That's the only way to get it, right?

gmilazzoitag

I've got the same issue with 7.1 release...Man Indifferent

The server side patch with the new jar file seems newer (4/29/2015) than the one on 7.1 installation files.

I've tried to apply the patch but I've got always the same error. With or without the patch...

The server is the same 7.0.2 with same environment where the patch worked. Just upgraded to 7.1

This java is a real nightmare!!!

 

Bye

 

30-04-2015 20-26-32.jpg

 

Regards,

ostiguy

The patch will break OCI 7.1.0 as the patch is both built for 7.0.2, and unnecessary for 7.1.0. I write this while having the Java client for 7.1.0 open on my laptop, running on Java 8u45

 

Giacomo - I would clear out the Java cache - this is always recommended if you are upgrading from one OCI version to another.

gmilazzoitag

Sorry, I've replied without refreshing the page.

Anyway I've got that error also before the patch with the original jar file. 

I'll do some test.

 

Bye

JBARBALACE

Good morning guys,

Thank you for all of the follow-up and feedback.  I was unexpectedly out of the office and haven't been able to attend this.

 

I did try a patch that ostiguy forwarded for 7.0.2, but I was still getting the error.  I'm going to be testing 7.1 next week to see if we can get a better response with Java (yes, a giant nightmare).  I'm glad to know that java8u45 is working with 7.1.

 

Thanks again for the feedback!

Julia

gmilazzoitag

Yep! Cleaned the java cache it works. On OCI server I did it manually in C:\Users\<running user>\AppData\LocalLow\Sun\Java\Deployment\cache for there's no Control Panel Java applet.
Smiley Happy

 

No issue at all running Java UI from desktop shortcut on the server itself.

Labor day? Yes. Working on OCI 7.1 lab Smiley Indifferent but just because here is raining!

CoozyBones

Has this issues been resolved?

 

I have OCI 7.0.2 build 164 and from Windows 7 client using Chrome and latest Java (8.0.45) the UI just will not complete. It downloads the app when first run and then nothing.

 

I can't use previous Java versions (no option in our company), so the previous solution is not possible.

 

What other options are their for configuring/changing annotations etc. Is there only the Java UI?

 

thanks in advance for suggestions/ideas/help.

ostiguy
Yes, this issue is resolved, but you resolve it by deploying a server side OCI patch - this patch will resolve the issue for all the Java client users of that OCI instance.The forthcoming OCI 7.0.3 and 7.1.0 releases will not need a patch. For annotating objects, there are a few different options: The OCI annotation import utility is a CLI jar tool that can annotate objects from a .CSV. This is the most common approach for customers who have a CMDB that has host .-> application relationships, and want to bring that data into OCI . There is now some REST API tooling that allows you to set annotations as of OCI 7.0.2 and higher. Not all objects are yet capable of being annotated this way. Finally, one can manually annotate objects in the Java client.

JBARBALACE

We are also testing OCI 7.0.2 build 164.  Although it runs fine from the OCI server, when we try to open it from a user workstation (Windows 7 Professional), we can't seem to find an appropriate jre7 update that will allow the Java UI to open.  We end up with the "unable to launch application" window.  We were fine when testing 7.0.1, but now that we are testing 7.0.2 it's not working at all.  We had a workaround of sorts for jre7u71, but that is not working now.  I've tried to downgrade to lower updates, tried 32-bit and 64-bit of most java updates, too.

 

If there is a server side patch available for 7.0.2, I would be very interested in giving that a try.  

 

Thank you!

Julia

justin_smith

Build 164 doesnt work for us either. We dont actually get an error but nothing happens when Java loads and you accept all the awesome java prompts.

 

7.1 is out but its a FCR, not sure I want to work THAT bad 🙂

ostiguy

Justin, have you obtained and deployed the patch for this issue?

CoozyBones

ok thanks...can you post the link to the patch please.

 

thanks

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

Public