SVNException: svn: SSL peer shut down incorrectly (1.391)
2 messages
Open this post in threaded view
Report Content as Inappropriate
SVNException: svn: SSL peer shut down incorrectly (1.391)
I have a Subversion checkout failure just after I upgrade Hudson from
1.383 to 1.391 and Subversion plugin from 1.20 to 1.23
This exception was raised in the middle of checkout.
& ERROR: Failed to update XXXXXXXXXXXXXXXXXX
& & org.tmatesoft.svn.core.SVNException: svn: SSL peer shut down
incorrectly
& & svn: REPORT request failed on '/XXXXXXXXXXXXXXXX/!svn/vcc/default'
& [...callstack deleted...]
& Caused by: javax.net.ssl.SSLException: SSL peer shut down
incorrectly
& [...callstack deleted...]
The full callstack is in the end of this message. It doesn't always
fail, but randomly. I've restarted all slave agents after upgrading
the master.
==========================================================
ERROR: Failed to update org.tmatesoft.svn.core.SVNException: svn: SSL peer shut down
incorrectly
svn: REPORT request failed on '/XXXXXXXXXXXXX/!svn/vcc/default'
& & & & at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:
& & & & at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:
& & & & at
org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:
& & & & at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:
& & & & at hudson.scm.subversion.UpdateUpdater
$TaskImpl.perform(UpdateUpdater.java:129)
& & & & at hudson.scm.subversion.WorkspaceUpdater
$UpdateTask.delegateTo(WorkspaceUpdater.java:137)
& & & & at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:
& & & & at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:
& & & & at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:
& & & & at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1925)
& & & & at hudson.remoting.UserRequest.perform(UserRequest.java:114)
& & & & at hudson.remoting.UserRequest.perform(UserRequest.java:48)
& & & & at hudson.remoting.Request$2.run(Request.java:270)
& & & & at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
& & & & at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
& & & & at java.util.concurrent.FutureTask.run(Unknown Source)
& & & & at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
& & & & at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
& & & & at hudson.remoting.Engine$1$1.run(Engine.java:58)
& & & & at java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLException: SSL peer shut down incorrectly
& & & & at com.sun.net.ssl.internal.ssl.InputRecord.readV3Record(Unknown
& & & & at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
& & & & at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown
& & & & at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(Unknown
& & & & at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source)
& & & & at java.io.BufferedInputStream.read1(Unknown Source)
& & & & at java.io.BufferedInputStream.read(Unknown Source)
& & & & at
org.tmatesoft.svn.core.internal.util.ChunkedInputStream.read(ChunkedInputStream.java:
& & & & at sun.nio.cs.StreamDecoder.readBytes(Unknown Source)
& & & & at sun.nio.cs.StreamDecoder.implRead(Unknown Source)
& & & & at sun.nio.cs.StreamDecoder.read(Unknown Source)
& & & & at java.io.InputStreamReader.read(Unknown Source)
& & & & at
org.tmatesoft.svn.core.internal.io.dav.http.XMLReader.read(XMLReader.java:
& & & & at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)
& & & & at org.apache.xerces.impl.XMLEntityScanner.scanContent(Unknown
& & & & at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanContent(Unknown
& & & & at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl
$FragmentContentDispatcher.dispatch(Unknown Source)
& & & & at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
& & & & at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
& & & & at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
& & & & at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
& & & & at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
& & & & at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:
& & & & at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:
& & & & ... 23 more
Open this post in threaded view
Report Content as Inappropriate
Re: SVNException: svn: SSL peer shut down incorrectly (1.391)
The same happens to me with SVNKit 1.8, outside the context of Jenkins. &:-(I'm using a proxy.Am Donnerstag, 13. Januar :02 UTC+1 schrieb Pere Martir:I have a Subversion checkout failure just after I upgrade Hudson from
1.383 to 1.391 and Subversion plugin from 1.20 to 1.23
This exception was raised in the middle of checkout.
You received this message because you are subscribed to the Google Groups &Jenkins Users& group.
To unsubscribe from this group and stop receiving emails from it, send an email to .
For more options, visit .
Loading...Java ssl连接错误，SSL peer shut down incorrectly怎么解决_百度知道
Java ssl连接错误，SSL peer shut down incorrectly怎么解决
种做个事后job定时清理吧，这样数据库之间可以通过数据库事务，可以通过在删的同时写入一个数据表，然后job通过这个表去删除图片，这个删除的时候就不需要事务了，下次再删除也没事（虽然其实已经没文件可以删除了），就算数据问题。当然貌似文件也是可以通过分布式事务的，删除成功，但数据没更新，现在一时间也找不，但这个资料之前有看过
其他类似问题
为您推荐：
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁Java ssl连接错误，SSL peer shut down incorrectly怎么解决_百度知道
Java ssl连接错误，SSL peer shut down incorrectly怎么解决
　　1.在CA机构申请的数字证书、根证书、二级证书都已经按要求导入到 myproject.keystore文件。　　2.接口方的公钥也已经导入myproject.trustore文件。　　3.使用openssl在授权服务器测试连接正常。　　4.使用接口方提供的测试demo在本地环境进行连接测试异常（ssh代理方式连接）。异常应该不会是代理的缘故，https可以通过代理方式访问。
其他类似问题
为您推荐：
peer的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁MQ 配置SSL，连接至队列管理器“QMEMBFE_BOA”失败最近使用mq需要连接mq服务器通道时使用ssl连接，按网上的教程配置了下，应用程序通过jms连接时，ssl握手失败。详细错误如下：Caused by: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ0018: 连接至队列管理器“QMEMBFE_BOA”失败，连接方式为“Client”，主机名为“localhos...最近使用mq需要连接mq服务器通道时使用ssl连接，按网上的教程配置了下，应用程序通过jms连接时，ssl握手失败。详细错误如下：Caused by: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ0018: 连接至队列管理器“QMEMBFE_BOA”失败，连接方式为“Client”，主机名为“localhost(32001)”。检查队列管理器是否已启动，如果正在以客户机方式运行，那么还要检查是否有侦听器在运行。请参阅链接的异常以获取更多信息。at com.ibm.msg.mon.internal.Reason.reasonToException(Reason.java:580)at com.ibm.msg.mon.internal.Reason.createException(Reason.java:216)at com.ibm.msg.client.wmq.internal.WMQConnection.(WMQConnection.java:418)at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection(WMQConnectionFactory.java:6772)at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:6151)at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection(JmsConnectionFactoryImpl.java:280)at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQConnectionFactory.java:6138)at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:115)at mon.jms.pool.JNDIJMSFactoryImpl$QueueConnectionFactoryBean.createQueueConnection(JNDIJMSFactoryImpl.java:54)at mon.jms.pool.JNDIJMSFactoryImpl.getQueueConnection(JNDIJMSFactoryImpl.java:28)at mon.jms.pool.JMSPool.createNewQueueConnection(JMSPool.java:224)at mon.jms.pool.JMSPool.getQueueConnectionHolder(JMSPool.java:119)at mon.jms.pool.JMSPool.getLongQueueSession(JMSPool.java:87)at mon.jms.pool.JMSPool.getLongQueueSession(JMSPool.java:81)at mon.jms.JMSCommon.readObjectMessage(JMSCommon.java:722)... 1 moreCaused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ 调用失败，完成代码为“2”（“MQCC_FAILED”），原因为“2397”（“MQRC_JSSE_ERROR”）。at com.ibm.msg.mon.internal.Reason.createException(Reason.java:204)... 14 moreCaused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9204: 与主机 'localhost(32001)' 的连接被拒绝。 [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2397;AMQ9771: SSL 握手失败。 [1=javax.net.ssl.SSLHandshakeException[Remote host closed connection during handshake],3=localhost/127.0.0.1:32001 (localhost),4=SSLSocket.startHandshake,5=default]],3=localhost(32001),5=RemoteTCPConnection.protocolConnect]at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1862)at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1144)at com.ibm.msg.client.wmq.internal.WMQConnection.(WMQConnection.java:337)... 13 moreCaused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9771: SSL 握手失败。 [1=javax.net.ssl.SSLHandshakeException[Remote host closed connection during handshake],3=localhost/127.0.0.1:32001 (localhost),4=SSLSocket.startHandshake,5=default]at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.protocolConnect(RemoteTCPConnection.java:1140)at com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConnection.java:682)at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSessionFromNewConnection(RemoteConnectionSpecification.java:347)at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSession(RemoteConnectionSpecification.java:259)at com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(RemoteConnectionPool.java:144)at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1491)... 15 moreCaused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshakeat com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:801)at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1089)at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1116)at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1100)at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection$6.run(RemoteTCPConnection.java:1110)at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection$6.run(RemoteTCPConnection.java:1103)at java.security.AccessController.doPrivileged(Native Method)at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.protocolConnect(RemoteTCPConnection.java:1101)... 20 moreCaused by: java.io.EOFException: SSL peer shut down incorrectlyat com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:782)... 27 more配置的过程是：我本来有个ca发的jks，服务器证书 ，里面都有签署者证书和服务器证书。在队列管理器的ssl下指定到该证书库。客户端调用的时候也先调用该证书库，再进行连接。mq 的通道配置如下 ：dis chl(BILL_SVR_CHL)& &&&1 : dis chl(BILL_SVR_CHL)AMQ8414: 显示通道细节。& &CHANNEL(BILL_SVR_CHL)& && && && && && & CHLTYPE(SVRCONN)& &ALTDATE()& && && && && && && &ALTTIME(15.32.47)& &COMPHDR(NONE)& && && && && && && && && &COMPMSG(NONE)& &DESCR( )& && && && && && && && && && &&&DISCINT(0)& &HBINT(300)& && && && && && && && && && &KAINT(AUTO)& &MAXINST()& && && && && && && & MAXINSTC()& &MAXMSGL()& && && && && && && & MCAUSER( )& &MONCHL(QMGR)& && && && && && && && && & RCVDATA( )& &RCVEXIT( )& && && && && && && && && && &SCYDATA( )& &SCYEXIT( )& && && && && && && && && && &SENDDATA( )& &SENDEXIT( )& && && && && && && && && &&&SHARECNV(10)& &SSLCAUTH(OPTIONAL)& && && && && && && & SSLCIPH(RC4_SHA_US)& &SSLPEER( )& && && && && && && && && && &TRPTYPE(TCP)有配置过mq ssl的大神米有，跪求指导。关注问题12回答技术经理
, 某集团公司参考：http://www-/support/do ... ynp=OCSSFKSJ&mync=RCause 2: Missing server personal certificate参考：Cause 2: Missing server personal certificate赞同软件开发工程师
, company回复 2# liushaoyi & & 有SIT服务器上已经连上了mq。但我现在本机环境 想搭建一个ssl的，之前按网上的设置都没成功。。。。有没有相关资料分享下。。。。回复
liushaoyi & & 有SIT服务器上已经连上了mq。但我现在本机环境 想搭建一个ssl的，之前按网上的设置都没成功。。。。有没有相关资料分享下。。。。赞同撰写回答软件开发工程师, company关注发布12回答9请稍候...