Active IQ Unified Manager Discussions

After 7.3.5 upgrade, no longer able to access Java functionality

Don_Childers
2,235 Views

I hate to even ask this since Java not working can be a million different things but after our upgrade from 7.3.1 to 7.3.5, even with the latest version of Java, no one can get into the Java section of OCI. I've made sure that my OCI entry in the Java security section is still there as well. Also tried uninstalling and reinstalling Java. Everything worked before the upgrade. Are there new Java requirements with 7.3.5?

 

Has anyone seen these errors when attempting to launch the Java console? The URL is our internal OCI website.

 

java.io.IOException: Server returned HTTP response code: 403 for URL: https://oci.providence.org/client/app/http-client.jnlp
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.doHeadRequestEX(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.checkUpdateAvailable(Unknown Source)
at com.sun.deploy.cache.ResourceProviderImpl.isUpdateAvailable(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)

 

Thanks for any advice. --Don

1 ACCEPTED SOLUTION

Don_Childers
1,935 Views

This turned out to be a Java version issue. OCI 7.3.5 supports Java 8u192, not the latest 8u221. It's noted in the OnCommand Insight 7.3 Release Notes. I missed it.

View solution in original post

3 REPLIES 3

AlexDawson
2,194 Views

Hi there! I had a quick look and couldn't find anything to say one way or the other on this.

 

I suggest you should probably log a case with our support team over this - hopefully we can help get you back up and running quickly.

Don_Childers
2,026 Views

Thanks. I'll open a case on this.

Don_Childers
1,936 Views

This turned out to be a Java version issue. OCI 7.3.5 supports Java 8u192, not the latest 8u221. It's noted in the OnCommand Insight 7.3 Release Notes. I missed it.

Public