Ibm cloud 访问dashDB数据源时Bluemix liberty运行时握手失败

当我试图从自动配置的liberty服务器（DB2驱动程序的深处）访问dashDb时，突然收到一条SSL错误消息。我已在部署的文件中验证默认密钥库是否自动配置到liberty服务器中

这里发生了什么

 java.security.cert.CertPathValidatorException: The certificate issued by CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US is not trusted; internal cause is: 
 [ERROR   ] CWPKI0022E: SSL HANDSHAKE FAILURE:  A signer with SubjectDN CN=*.services.dal.bluemix.net, O=International Business Machines Corporation, L=Armonk, ST=New York, C=US was sent from the target host.  The signer might need to be added to local trust store /home/vcap/app/wlp/usr/servers/BluemixServer/resources/security/key.jks, located in SSL configuration alias defaultSSLConfig.  The extended error message from the SSL handshake exception is: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is
 [err] java.sql.SQLNonTransientException: [jcc][t4][2030][11211][4.19.49] A communication error occurred during operations on the connection's underlying socket, socket input stream, 
 or socket output stream.  Error location: Reply.fill() - socketInputStream.read (-1).  Message: java.security.cert.CertificateException: PKIXCertPathBuilderImpl could not build a valid CertPath.. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499
 [err]     at com.ibm.db2.jcc.am.kd.a(Unknown Source)

---

上周五对dashDB进行了更改，这增强了访问dashDB的应用程序密码规范的安全性要求。如果您的应用程序在上周之前工作，而现在不工作，则可能需要更新密码

请通过

参阅IBM技术报告。我们可以使用以下Liberty for java构建包之一连接到dashDB。请尝试重新部署您的应用程序，并确保数据库URI的结尾为：sslConnection=true

构建包

• buildpack_liberty-for-java_v3.8-20170308-1507.zip（最新）
• buildpack_liberty-for-java_v3.4.1-20161030-2241.zip（最旧）

---

谢谢。这种影响以前有没有通知过？只是为了检查我为什么错过了这个：）Bluemix状态页面上发布了一个通知。2017年3月8日上午10:33更新dashDB服务更新说明：IBM dashDB for Analytics Entry和SMP服务将接受定期维护。在此维护窗口期间，dashDB服务的最新更新将应用于可靠性、功能增强和安全性。