Fisheye/Crucible svn: E175002: SSL peer shut down incorrectly
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
The indexing of a SVN repository stops, and the following can be seen in the repository Summary, under Recent Errors:
1
2
3
4
5
6
7
8
9
10
11
12
Repository paused due to error
com.cenqua.fisheye.rep.RepositoryClientException:
java.lang.IllegalStateException: Can't overwrite cause with
org.tmatesoft.svn.core.SVNException: svn: E175002: SSL peer shut down
incorrectly svn: E175002: REPORT request failed on
'/repos/svn-repo/!svn/vcc/default' java.lang.IllegalStateException: Can't
overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E175002:
SSL peer shut down incorrectly svn: E175002: REPORT request failed on
'/repos/svn-repo/!svn/vcc/default'
org.apache.subversion.javahl.ClientException: svn: E175002: SSL peer
shut down incorrectly svn: E175002: REPORT request failed on
'/repos/svn-repo/!svn/vcc/default'The following appears in the atlassian-fisheye-yyyy-mm-dd.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
2016-08-24 12:00:00,000 WARN [InitPing2 svn-repo ] fisheye BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo svn-repo due to class com.cenqua.fisheye.rep.RepositoryClientException - java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E175002: SSL peer shut down incorrectly
svn: E175002: REPORT request failed on '/svn-repo/!svn/vcc/default'
com.cenqua.fisheye.rep.RepositoryClientException: java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E175002: SSL peer shut down incorrectly
svn: E175002: REPORT request failed on '/svn-repo/!svn/vcc/default'
at com.cenqua.fisheye.svn.SvnThrottledClient.executeNoThrottle(SvnThrottledClient.java:189) [fisheye.jar:?]
at com.cenqua.fisheye.svn.SvnThrottledClient.execute(SvnThrottledClient.java:158) [fisheye.jar:?]
at com.cenqua.fisheye.svn.SvnThrottledClient.diffSummarize(SvnThrottledClient.java:228) [fisheye.jar:?]
at com.atlassian.fisheye.svn.Svn2Infill2Processor.summarizeDiff(Svn2Infill2Processor.java:312) [fisheye.jar:?]
...
Caused by: java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E175002: SSL peer shut down incorrectly
svn: E175002: REPORT request failed on '/svn-repo/!svn/vcc/default'
...
Caused by: org.apache.subversion.javahl.ClientException: svn: E175002: SSL peer shut down incorrectly
svn: E175002: REPORT request failed on '/svn-repo/!svn/vcc/default'
at org.apache.subversion.javahl.ClientException.fromException(ClientException.java:117) [svnkit-javahl16-1.9.0-r10609-atlassian-hosted.jar:?]
at org.tmatesoft.svn.core.javahl17.SVNClientImpl.getClientException(SVNClientImpl.java:1535) [svnkit-javahl16-1.9.0-r10609-atlassian-hosted.jar:?]
... 12 more
2016-08-24 12:00:00,001 INFO [InitPing2 svn-repo ] fisheye RepositoryEngine-startPause - Repository scanner paused. Error: java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E175002: SSL peer shut down incorrectly
svn: E175002: REPORT request failed on '/svn-repo/!svn/vcc/default'Cause
The SSL connection was cut off between your repository server and Fisheye/Crucible while Fisheye/Crucible was in the middle of pulling and indexing.
By default, both SVN and Fisheye have a connection timeout of 60 minutes, so it's possible that the Web/Proxy Server hosting the SVN repository has reached its timeout.
Resolution
Review the entire set of proxy or web servers between Fisheye and the SVN server to make sure that the connection is not interrupted by any of them.
Increase the connection timeout in any of the intermediate applications (including but not limited to):
a Web proxy
a Proxy Server
the Apache server
The SVN operations taking longer than an hour time out provides useful details on how to increase the timeouts and some alternatives to consider.
Was this helpful?