SVN indexing fails in Fisheye with "chunked stream ended unexpectedly" warning in logs

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

A Fisheye repository cannot be indexed.

The following appears in the atlassian-fisheye-YYYY-MM-DD.log log file:

WARN  [InitPing1 <repository_name> ] fisheye BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo <repository_name> due to class com.cenqua.fisheye.rep.RepositoryClientException - java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E175002: chunked stream ended unexpectedly
    svn: E175002: REPORT request failed on '/svn/root/!svn/folder/default'
com.cenqua.fisheye.rep.RepositoryClientException: java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E175002: chunked stream ended unexpectedly
    svn: E175002: REPORT request failed on '/svn/root/!svn/folder/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:?]
...
Caused by: java.lang.IllegalStateException: Can't overwrite cause with org.tmatesoft.svn.core.SVNException: svn: E175002: chunked stream ended unexpectedly
    svn: E175002: REPORT request failed on '/svn/root/!svn/folder/default'
...
Caused by: org.apache.subversion.javahl.ClientException: svn: E175002: chunked stream ended unexpectedly
    svn: E175002: REPORT request failed on '/svn/root/!svn/folder/default'
	at org.apache.subversion.javahl.ClientException.fromException(ClientException.java:117) [svnkit-javahl16-1.9.0-r10609-atlassian-hosted.jar:?]

Cause

There are several potential causes for this problem:

  • the connection to the SVN server is being interrupted by a web server 
  • a web server is setting a limit for the number of bytes that can be transferred.

Workaround

Change the configuration to connect Fisheye by using the file:// protocol instead of http://.

Resolution

Configure the web server to avoid the connection from being interrupted

Last modified on Aug 2, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.