Java 日历API调用开始生成；“SSL对等关闭”；

我有一个中间件（由Tibco ActiveMatrix BusinessWorks开发，但我认为它不是很重要），它已经工作了几个月，突然在2020-10-17开始在大量请求（约8000个）上失败，错误如下：

javax.ws.rs.ProcessingException: javax.net.ssl.SSLException: SSL peer shut down incorrectly

你知道为什么这个错误会突然发生吗？怎么解决？提前谢谢

完整堆栈跟踪：

Job-3158 Error in [BusinessProcesses/AgendasSecurises/Helpers/Gmail/Get Event.process/Get Event] Activity invocation failed at com.tibco.pe.plugin.Activity.postEval(Unknown Source) at com.tibco.pe.plugin.Activity.postEval(Unknown Source) at com.tibco.pe.core.TaskImpl.eval(Unknown Source) at com.tibco.pe.core.Job.a(Unknown Source) at com.tibco.pe.core.Job.k(Unknown Source) at com.tibco.pe.core.JobDispatcher$JobCourier.a(Unknown Source) at com.tibco.pe.core.JobDispatcher$JobCourier.run(Unknown Source) caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLException: SSL peer shut down incorrectly at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:287) at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:252) at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:701) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:228) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444) at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:697) at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:420) at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:316) at com.tibco.plugin.json.activities.RestActivity.doGet(RestActivity.java:485) at com.tibco.plugin.json.activities.RestActivity.doService(RestActivity.java:473) at com.tibco.plugin.json.activities.RestActivity$1.run(RestActivity.java:418) at com.tibco.pe.util.ThreadPool$ThreadPoolThread.run(Unknown Source) Caused by: javax.net.ssl.SSLException: SSL peer shut down incorrectly at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:596) at sun.security.ssl.InputRecord.read(InputRecord.java:532) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:990) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1388) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1416) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1400) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352) at org.glassfish.jersey.client.internal.HttpUrlConnector._apply(HttpUrlConnector.java:399) at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:285) ... 13 more

---

这很可能是在提到的日期服务器端发生了一些变化

它可能是证书的更改，也可能是一些需要使用健壮加密库的更改（例如，TLS 1.2现在可能是强制性的）

如果您使用的是最新版本的BusinessWorks TLS 1.2，则默认情况下应启用。如果您使用的是旧版本（6.3.x），则可能必须使用以下内容编辑bwappnode.tra文件：

extended.properties=-Xmx1024m-Xms128m-XX:+heapdumponootfmemoryerror-Dhttps.protocols=TLSv1.1，TLSv1.2

您可以使用以下TIBCO KB中的元素来获取更多跟踪和调试问题：

---

这很可能是在提到的日期服务器端发生了一些变化

它可能是证书的更改，也可能是一些需要使用健壮加密库的更改（例如，TLS 1.2现在可能是强制性的）

如果您使用的是最新版本的BusinessWorks TLS 1.2，则默认情况下应启用。如果您使用的是旧版本（6.3.x），则可能必须使用以下内容编辑bwappnode.tra文件：

extended.properties=-Xmx1024m-Xms128m-XX:+heapdumponootfmemoryerror-Dhttps.protocols=TLSv1.1，TLSv1.2

您可以使用以下TIBCO KB中的元素来获取更多跟踪和调试问题：