Article ID: 121023, created on Apr 10, 2014, last review on May 11, 2014

  • Applies to:
  • Virtual Automation 6.0

Symptoms

VNC console doesn't work for Virtual Machines in PVA, if it is accessed by its FQDN, for example, https://pva.pcs.test:4648.

The console works correctly, if PVA is accessed by its IP address.

With enabled Java tracing it produces the following errors :

network: Cache entry not found [url: https://pva.pcs.test:4648/vz/rdp/VncViewer.jar, version: null]
network: Connecting https://pva.pcs.test:4648/vz/rdp/VncViewer.jar with proxy=DIRECT
network: Connecting http://pva.pcs.test:4648/ with proxy=DIRECT
...
javax.net.ssl.SSLProtocolException: handshake alert:  unrecognized_name
...
java.lang.ClassNotFoundException: com.tightvnc.vncviewer.VncViewer

Cause

An SSL handshake alert occurs, if the referenced hostname doesn't match the one, defined in Apache configuration on the PVA MN server.

Related discussion: https://community.oracle.com/message/10332444.
Oracle Java bug reference: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7127374

Java Runtime Environment versions 7 and 8 are affected by the problem.

Resolution

Add ServerName directive to /etc/httpd/conf.d/ssl.conf file on PVA MN that will be mapped to the FQDN and port 4648.

Example:

[root@pva ~]# grep ServerName /etc/httpd/conf.d/ssl.conf
# #ServerName www.example.com:443
ServerName pva.pcs.test:4648

Search Words

ClassNotFoundException

com.tightvnc.vncviewer.VncViewer

319940068c5fa20655215d590b7be29b 2897d76d56d2010f4e3a28f864d69223 0889ab60fa6494de107aa7338c3c38b6

Email subscription for changes to this article
Save as PDF