Symptoms: 

Getting the SSLHandshakeException WARN message every 2-4 seconds in ever-growing WebView logs.

[WARN] [org.mortbay.log] EXCEPTION
javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:980)
        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1363)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1391)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1375)
        at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:675)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
        at sun.security.ssl.InputRecord.read(InputRecord.java:505)
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:961)

        ... 5 more

Environment:  

Introscope 10.x

 Cause: 

 This is a client connection issue where the client side of the SSL connection brought down the connection before the SSL handshake completed. This can happen if the browser sends a request but closes before the server can reply back. The error can be specifically caused if you have not updated the default certificate used by Webview (as the connection is not trusted on the client side).

Workaround:

 Use one of the following options:

 1. Adding a certificate trusted on the client side should resolve the issue.

 2. Change logging from

log4j.logger.org.mortbay=ERROR, console, logfile

 to

log4j.logger.org.mortbay=INFO, console, logfile

 Additional Information:

 There should be no functional impact caused by the warnings, so you can safely ignore them.

Release: CEMUGD00200-10.1-Introscope to CA Application-Performance Management-Upgrade Mai
Component: