Symptom
When executing a monitoring probe against an application server running SSL (self-signed certificate), the probe result fails and gives the following exception:
Probe Name: BI launch pad
Result: Failed
Duration: 319 msec
Diagnostic Messages: Attempting to connect to https://localhost:8443/BOE/BI
Could not connect to https://localhost:8443/BOE/BI. Ensure that the URL Base parameter in the properties of this probe is correct.
Exception : javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching localhost found
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1747)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:241)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:235)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1209)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:135)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:943)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199)
at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:476)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:133)
at com.businessobjects.monitoring.probe.ProbeInfoView.execute(ProbeInfoView.java:178)
at com.businessobjects.monitoring.probe.ProbeInfoView.executeDiagnosticProbe(ProbeInfoView.java:82)
at com.businessobjects.sdk.monitoring.probe.DiagnosticProbeManager$DiagnosticProbeTask.call(DiagnosticProbeManager.java:201)
at com.businessobjects.sdk.monitoring.probe.DiagnosticProbeManager$DiagnosticProbeTask.call(DiagnosticProbeManager.java:177)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.lang.Thread.run(Thread.java:761)
Caused by: java.security.cert.CertificateException: No name matching localhost found
at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:210)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:77)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:264)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:250)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1188)
... 17 more
|
Read more...
Environment
- SAP BusinessObjects Business Intelligence Platform 4.0 / 4.1
Product
SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.0, feature pack 3 ; SAP BusinessObjects Business Intelligence platform 4.1
Keywords
monitoring, probe, BI Launchpad, javax.net.ssl.SSLHandshakeException, java.security.cert.CertificateException, matching, name, hostname, localhost, CN, SSL, Tomcat, canonical, 4.0, 4.1 , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , BI-BIP-MON , BI platform monitoring , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview