This is my first time trying to setup FishEye and I have pointed it to an SVN repo. During the initial indexing, it appears to get stuck and timeout on one of the commands (the top one in the below screenshot, it times out after about 2 hours ~720000ms):
2014-12-01 11_46_11-FishEye and Crucible_ Administration.png
Running the problematic command manually, timings:
$ time svn log -r 1:HEAD http://10.3.19.102:3690/svn/kts/@HEAD > /dev/null real 0m7.961s user 0m0.162s sys 0m0.038s
Stack dump from fisheye log after the command times out (note, 14531 is head revision):
2014-12-01 09:22:39,866 ERROR [InitPing2 KTS ] fisheye BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo KTS due to class com.cenqua.fisheye.rep.RepositoryClientException - org.apache.subversion.javahl.ClientException: svn: E175002: timed out waiting for server svn: E175002: REPORT request failed on '/svn/kts/!svn/bc/14531' com.cenqua.fisheye.rep.RepositoryClientException: org.apache.subversion.javahl.ClientException: svn: E175002: timed out waiting for server svn: E175002: REPORT request failed on '/svn/kts/!svn/bc/14531' at com.cenqua.fisheye.svn.SvnThrottledClient.executeNoThrottle(SvnThrottledClient.java:186) at com.cenqua.fisheye.svn.SvnThrottledClient.execute(SvnThrottledClient.java:155) at com.cenqua.fisheye.svn.SvnThrottledClient.logMessages(SvnThrottledClient.java:137) at com.atlassian.fisheye.svn.Svn2RepositoryClient.getChangesetIds(Svn2RepositoryClient.java:129) at com.atlassian.fisheye.svn.Svn2Scanner.doChangesetScan(Svn2Scanner.java:272) at com.atlassian.fisheye.svn.Svn2Scanner.slurpRepository(Svn2Scanner.java:205) at com.atlassian.fisheye.svn.Svn2Scanner.doSlurpTransaction(Svn2Scanner.java:182) at com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:73) at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:86) at com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:414) at com.cenqua.fisheye.rep.ping.IndexingPingRequest.doRequest(IndexingPingRequest.java:27) at com.cenqua.fisheye.rep.ping.IncrementalPingRequest.doRequest(IncrementalPingRequest.java:30) at com.cenqua.fisheye.rep.ping.PingRequest$1.run(PingRequest.java:55) at com.cenqua.fisheye.util.NamedExecution.run(NamedExecution.java:27) at com.cenqua.fisheye.rep.ping.PingRequest.process(PingRequest.java:52) at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(RepositoryHandle.java:213) at com.cenqua.fisheye.rep.RepositoryHandle.access$100(RepositoryHandle.java:57) at com.cenqua.fisheye.rep.RepositoryHandle$2.run(RepositoryHandle.java:169) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.subversion.javahl.ClientException: svn: E175002: timed out waiting for server svn: E175002: REPORT request failed on '/svn/kts/!svn/bc/14531' at org.apache.subversion.javahl.ClientException.fromException(ClientException.java:68) at org.tmatesoft.svn.core.javahl17.SVNClientImpl.getClientException(SVNClientImpl.java:1492) at org.tmatesoft.svn.core.javahl17.SVNClientImpl.logMessages(SVNClientImpl.java:295) at org.apache.subversion.javahl.SVNClient.logMessages(SVNClient.java:82) at com.cenqua.fisheye.svn.SvnThrottledClient$2.call(SvnThrottledClient.java:143) at com.cenqua.fisheye.svn.SvnThrottledClient$2.call(SvnThrottledClient.java:138) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at com.cenqua.fisheye.svn.SvnTask.access$101(SvnTask.java:14) at com.cenqua.fisheye.svn.SvnTask$1.run(SvnTask.java:36) at com.cenqua.fisheye.util.NamedExecution.run(NamedExecution.java:27) at com.cenqua.fisheye.svn.SvnTask.run(SvnTask.java:31) ... 3 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: timed out waiting for server svn: E175002: REPORT request failed on '/svn/kts/!svn/bc/14531' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:106) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:90) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:764) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:334) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:324) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1007) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1038) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1258) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.javahl17.SVNClientImpl.logMessages(SVNClientImpl.java:293) ... 12 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(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:75) at java.util.zip.InflaterInputStream.fill(Unknown Source) at java.util.zip.InflaterInputStream.read(Unknown Source) at java.util.zip.GZIPInputStream.read(Unknown Source) 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:39) at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.skipString(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) 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.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:898) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:863) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:220) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:463) ... 25 more
This doesn't strike me as a simple "time outs not long enough" issue as the command runs pretty quickly. Also, after the first second of starting the indexing, I see the CPU usage on the system fall to ~0 so it doesn't seem like any work is being performed. Connection seems fine since the other commands appear to finish successfully and quickly. FishEye is running on the same server as the SVN repo (10.3.19.102 == localhost).
SVN server (CollabNet) version: 1.8.10-3908.133
FishEye 3.6.1 20141030150539
Hi Gary,
Can you please give this KB article a try:
https://confluence.atlassian.com/display/FISHKB/SVN+Operations+Taking+Longer+than+an+Hour+Time+Out
Please let us know how it goes.
Kind regards,
Felipe Kraemer
Do you think it's a timeout issue? 2 hours should be more than enough for it to do an operation which takes a few seconds. The fact that the CPU is idle makes me think that more time would not help :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.