将jdk从8u221升级到8u241获得java.net.SocketException:管道破裂（写入失败）异常

在将JDK8从8u221升级到8u241（小版本更改）后，出现以下异常。请告诉我哪里出了问题，但它在8u231中工作。请引导我

WARNING: Unable to synchronize with remote stored reports. Some stored report might not be available.
    com.watch4net.apg.report.scheduling.gui.ReportSchedulerNotAvailableException: Unable to connect to the Task-Scheduler with URL 'https://localhost:48443/'!
        at com.watch4net.apg.report.scheduling.gui.TaskReportScheduler.updateTaskSchedulerModule(TaskReportScheduler.java:300)
        at com.watch4net.apg.report.scheduling.gui.TaskReportScheduler.setTaskSchedulerConnection(TaskReportScheduler.java:170)
        at com.watch4net.apg.report.scheduling.gui.ReportSchedulerUtils.getReportSchedulerIfAvailable(ReportSchedulerUtils.java:130)
        at com.watch4net.apg.report.scheduling.gui.ReportSchedulerUtils.isSchedulerServerDisabled(ReportSchedulerUtils.java:268)
        at com.watch4net.apg.v2.gui.stats.FrontendStats.initialize(FrontendStats.java:156)
        at com.watch4net.apg.v2.gui.stats.FrontendStats$ApplicationListener.onStartup(FrontendStats.java:116)
        at com.watch4net.apg.common.util.ApplicationListenerUtils.startup(ApplicationListenerUtils.java:54)
        at com.watch4net.apg.v2.gui.servlet.listener.ApgListener.contextInitialized(ApgListener.java:741)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4699)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5165)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:614)
        at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1823)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.watch4net.apg.report.scheduling.gui.ReportSchedulerNotAvailableException: Unable to retrieve the 'task-scheduler' module!
        at com.watch4net.apg.report.scheduling.gui.WebserviceCommunicator.getTaskSchedulerModule(WebserviceCommunicator.java:82)
        at com.watch4net.apg.report.scheduling.gui.TaskReportScheduler.updateTaskSchedulerModule(TaskReportScheduler.java:296)
        ... 20 more
Caused by: com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.SocketException: Broken pipe (Write failed)
        at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:117)
        at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:208)
        at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:130)
        at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:124)
        at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121)
        at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035)
        at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004)
        at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862)
        at com.sun.xml.internal.ws.client.Stub.process(Stub.java:448)
        at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:178)
        at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
        at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77)
        at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147)
        at com.sun.proxy.$Proxy42.getModules(Unknown Source)
        at com.watch4net.apg.report.scheduling.gui.WebserviceCommunicator.getTaskSchedulerModule(WebserviceCommunicator.java:70)
        ... 21 more
Caused by: java.net.SocketException: Broken pipe (Write failed)
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
        at sun.security.ssl.OutputRecord.writeBuffer(OutputRecord.java:431)
        at sun.security.ssl.OutputRecord.write(OutputRecord.java:417)
        at sun.security.ssl.SSLSocketImpl.writeRecordInternal(SSLSocketImpl.java:879)
        at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:850)
        at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:720)
        at sun.security.ssl.Handshaker.sendChangeCipherSpec(Handshaker.java:1144)
        at sun.security.ssl.ClientHandshaker.sendChangeCipherAndFinish(ClientHandshaker.java:1281)
        at sun.security.ssl.ClientHandshaker.serverHelloDone(ClientHandshaker.java:1191)
        at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:369)
        at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
        at sun.security.ssl.Handshaker.process_record(Handshaker.java:965)
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064)
        at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
        at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
        at`enter code here` 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.getOutputStream0(HttpURLConnection.java:1340)
        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1315)
        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:264)
        at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:104)
        ... 35 more

---

你确定你唯一改变的是JDK吗？在大多数情况下，“断管”表示客户端意外地关闭了连接，而该连接只有在服务器尝试写入流时才被检测到-因此我要检查客户端是否以及为什么这样做。@Thomas-SSL协商期间管道破裂通常表示一端决定无法与另一端协商一组令人满意的参数。是吗你照我的建议去做？根据发行说明，8u241中有许多与安全相关的更改。但是您提供的信息不允许我们将您的问题与特定的更改联系起来。。。或者暗示一个修正。但是如果你遵循我之前的建议，可能会有更多的线索。发行说明：错误修复：由于连接在SSL/TLS握手过程中断开，并且正如Stephen C所指出的，在Java 8 update 241中TLS安全性已经加强，我倾向于相信两者是相关的。首先，我将尝试确定正在访问的URL是否返回一个证书，该证书的公用名与URL本身中的主机名完全匹配。您确定唯一更改的是JDK吗？在大多数情况下，“断管”意味着客户端意外关闭了只有当服务器试图写入流时才检测到的连接，因此我将检查客户端是否和为什么要这样做。@Thomas-SSL协商期间的一个断管通常意味着一端已决定无法与另一端协商一组满意的参数。是否你照我的建议去做？根据发行说明，8u241中有许多与安全相关的更改。但是您提供的信息不允许我们将您的问题与特定的更改联系起来。。。或者暗示一个修正。但是如果你遵循我之前的建议，可能会有更多的线索。发行说明：错误修复：由于连接在SSL/TLS握手过程中断开，并且正如Stephen C所指出的，在Java 8 update 241中TLS安全性已经加强，我倾向于相信两者是相关的。我将首先尝试确定正在访问的URL是否返回一个证书，该证书的公用名与URL本身中的主机名完全匹配。