Error in HudsonBuildLoopRunnable.isValidEngineConnection SSLHandshakeException
Our jazz log is getting flooded with these messages and although I believe I have deactivated all build engines that try to connect to bad jenkins servers, it is still happening. I slowed it down in the advanced properties to every 5 minutes instead of 15 seconds. How can I determine where this request is being initiated from? RTC 4.0.4
2016-05-05 12:05:25,717 [jazz: AsynchronousTaskRunner-4 @@ 12:05] ERROR com.ibm.rational.connector.hudson - Error in HudsonBuildLoopRunnable.isValidEngineConnection() javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:214) at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:645) at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:138) at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:268) at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:165) at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:27) at com.ibm.net.ssl.www2.protocol.https.b.connect(b.java:34) at com.ibm.rational.hudson.team.internal.service.HudsonConnectionHelper.getHTTPConnection(HudsonConnectionHelper.java:205) at com.ibm.rational.hudson.team.internal.service.HudsonConnectionHelper.getHTTPConnection(HudsonConnectionHelper.java:116) at com.ibm.rational.hudson.team.internal.service.HudsonConnectionHelper.getHTTPConnection(HudsonConnectionHelper.java:90) at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopRunnable.isValidEngineConnection(HudsonBuildLoopRunnable.java:508) at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopRunnable.getHandlingHudsonEngine(HudsonBuildLoopRunnable.java:419) at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopRunnable.processRequest(HudsonBuildLoopRunnable.java:128) at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopRunnable.run(HudsonBuildLoopRunnable.java:114) at com.ibm.rational.hudson.team.internal.service.HudsonBuildLoopScheduledTask.runTask(HudsonBuildLoopScheduledTask.java:43) at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:88) at sun.reflect.GeneratedMethodAccessor209.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy447.executeTask(Unknown Source) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:158) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:119) at java.lang.Thread.run(Thread.java:761) Caused by: java.io.EOFException: SSL peer shut down incorrectly at com.ibm.jsse2.b.a(b.java:228) at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:120) ... 25 more |
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.