Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Exception: java.lang.ClassNotFoundException: com.netapp.admin.FilerHTTPConfigUIApplet.class

2009-09-10
10:29 AM
12,559 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We started getting this Java error in FilerView today. One guy here seems to have resolved it by downgrading to Java 5. Are there any other workarounds?
load: class com/netapp/admin/FilerHTTPConfigUIApplet.class not found.
java.lang.ClassNotFoundException: com.netapp.admin.FilerHTTPConfigUIApplet.class
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLException: Received fatal alert: bad_record_mac
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.sun.net.ssl.internal.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 java.net.HttpURLConnection.getResponseCode(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.getBytes(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.access$000(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
... 7 more
Exception: java.lang.ClassNotFoundException: com.netapp.admin.FilerHTTPConfigUIApplet.class
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Michael,
Take a look at:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=234824
This may provide you another work around without having to downgrade to
a prior version
of Java.
Best Regards,
-paul
For 7.3.2RC1 and later:
http://now.netapp.com/NOW/knowledge/docs/ontap/rel732rc1/html/ontap/sysadmin/frameset.html
4 REPLIES 4
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Michael,
Take a look at:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=234824
This may provide you another work around without having to downgrade to
a prior version
of Java.
Best Regards,
-paul
For 7.3.2RC1 and later:
http://now.netapp.com/NOW/knowledge/docs/ontap/rel732rc1/html/ontap/sysadmin/frameset.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Disabling SSL worked.
options httpd.admin.ssl.enable off
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Simply disabling secure access as a workaround is not exactly what I would call a solution. I was able to solve the problem this way:
On your Windows box, open the Control Panel and pick "Java". Open the "Advanced" tab and expand "Security". Uncheck "Use TLS 1.0".
Java applets worked fine from that monent on.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem is due the TLS setting in Java and not with the Data ONTAP configuration. If you have JRE 1.6 and above you need to do the following
To resolve this issue, disable TLS1.0 from Java by doing the following:
- Select the following:
Control Panel - > Java - > Advanced Settings Tab - > Security List - Uncheck the TLS1.0 box.
- Restart the browser (Kill all instance and start new)
More info : https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb34698
If you are already in 7.3.2 and above then TLS has been supported in Data ONTAP (options tls.enable) itself .You don’t need to go by the workaround in KB, you can have TLS enabled in Java by keeping ONTAP TLS enabled. NOW online help can be used for helping you to understand and configure TLS can be found from the the following link
Thanks
Daniel
