Avamar: Unable to Launch Avamar Administrator JNLP with Java 1.8.0_481

After updating Java to version 1.8.0_481 on the user’s Windows machine, it is no longer possible to launch Avamar Administrator using the JNLP file.

1. On the Windows machine, confirm that the installed Java version is 1.8.0_481.

java -version

C:\>java -version
java version "1.8.0_481"
Java(TM) SE Runtime Environment (build 1.8.0_481-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.481-b10, mixed mode)
C:\>

2. Access the Avamar webpage:
   https://<Avamar_IP_Address>/dtlt/home.html
3. Click the Administrator hyperlink to download the administrator.jnlp file.
4. Open the JNLP file and confirm that it is being launched using Java.
5. Attempt to log in.
6. The error described in the screenshot appears.

"Invalid Certificate. Install a valid certificate and try again. You can use the Java Control Panel to import certificate"

7. The log file /usr/local/avamar/var/mc/server_log/mcserver.log.0 shows:

FINE: RMI TCP Connection(1982584)-192.168.1.110: terminated with exception:
javax.net.ssl.SSLException: Fatal Alert received: Certificate Unknown
        at com.rsa.sslj.x.aI.a(Unknown Source)
        at com.rsa.sslj.x.aI.a(Unknown Source)
        at com.rsa.sslj.x.aI.a(Unknown Source)
        at com.rsa.sslj.x.ap.c(Unknown Source)
        at com.rsa.sslj.x.ap.b(Unknown Source)
        at com.rsa.sslj.x.ap.b(Unknown Source)
        at com.rsa.sslj.x.al.read(Unknown Source)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
        at java.io.DataInputStream.readInt(DataInputStream.java:387)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:727)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)03/09-10:21:09.00246 [RMI TCP Connection(1982585)-192.168.1.110#1343977] sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0
FINE: RMI TCP Connection(1982585)-10.16.107.15: terminated with exception:
javax.net.ssl.SSLException: Ciphertext is too large in received TLS record
        at com.rsa.sslj.x.aI.b(Unknown Source)
        at com.rsa.sslj.x.aI.a(Unknown Source)
        at com.rsa.sslj.x.aI.a(Unknown Source)
        at com.rsa.sslj.x.ap.c(Unknown Source)
        at com.rsa.sslj.x.ap.b(Unknown Source)
        at com.rsa.sslj.x.ap.b(Unknown Source)
        at com.rsa.sslj.x.al.read(Unknown Source)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
        at java.io.DataInputStream.readInt(DataInputStream.java:387)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:727)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)
Caused by: com.rsa.sslj.x.aL: Ciphertext is too large in received TLS record

This issue occurs for any Avamar version. Engineering is investigating this behavior.

Alternatives

1. Use the installable version of Avamar Administrator, which includes an embedded Java version (1.8.0_202).
2. Use the Avamar User Interface (AUI).

Workarounds

1. Set the parameter rmi_over_ssl to false in the file /usr/local/avamar/var/mc/server_data/mcserver.xml and then restart the Management Console Service (MCS).
2. If modifying the parameter is not possible, use OpenWebStart (External Link) to open the JNLP file.