SVN repository indexing fails if using JavaHL after upgrading to 3.0.1
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
Symptoms
After upgrading Fisheye/Crucible to 3.0.1, this NullPointerException may appear in the atlassian-fisheye.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
2013-06-10 09:46:35,067 ERROR [IncrementalPinger1 SVN] fisheye BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo SVN due to class com.cenqua.fisheye.rep.RepositoryClientException - java.lang.NullPointerException
com.cenqua.fisheye.rep.RepositoryClientException: java.lang.NullPointerException
at com.cenqua.fisheye.svn.SvnThrottledClient.executeNoThrottle(SvnThrottledClient.java:163)
at com.cenqua.fisheye.svn.SvnThrottledClient.execute(SvnThrottledClient.java:132)
at com.cenqua.fisheye.svn.SvnThrottledClient.logMessages(SvnThrottledClient.java:120)
at com.atlassian.fisheye.svn.Svn2Scanner.processNonIndexedRange(Svn2Scanner.java:1004)
at com.atlassian.fisheye.svn.Svn2Scanner.upgradeCountEmptyChangesets(Svn2Scanner.java:937)
at com.atlassian.fisheye.svn.Svn2Scanner.slurpRepository(Svn2Scanner.java:195)
at com.atlassian.fisheye.svn.Svn2Scanner.doSlurpTransaction(Svn2Scanner.java:177)
at com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:85)
at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:92)
at com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:408)
at com.cenqua.fisheye.rep.ping.IndexingPingRequest.doRequest(IndexingPingRequest.java:25)
at com.cenqua.fisheye.rep.ping.IncrementalPingRequest.doRequest(IncrementalPingRequest.java:30)
at com.cenqua.fisheye.rep.ping.PingRequest.process(PingRequest.java:58)
at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(RepositoryHandle.java:228)
at com.cenqua.fisheye.rep.RepositoryHandle.access$100(RepositoryHandle.java:59)
at com.cenqua.fisheye.rep.RepositoryHandle$2.run(RepositoryHandle.java:185)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at com.atlassian.fisheye.svn.Svn2Scanner$10.singleMessage(Svn2Scanner.java:1009)
at org.tigris.subversion.javahl.SVNClient.logMessages(Native Method)
at org.tigris.subversion.javahl.SVNClient.logMessages(SVNClient.java:313)
at com.cenqua.fisheye.svn.SvnThrottledClient$2.call(SvnThrottledClient.java:124)
at com.cenqua.fisheye.svn.SvnThrottledClient$2.call(SvnThrottledClient.java:121)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at com.cenqua.fisheye.svn.SvnTask.run(SvnTask.java:32)
... 3 more
2013-06-10 09:46:35,073 ERROR [IncrementalPinger1 SVN] fisheye RepositoryEngine-startPause - Repository scanner paused.Cause
The error occurs in the Svn2Scanner when JavaHL passes in a null value for the changepaths collection of an svn log operation.
This is being tracked in our development issue tracker: FE-4687 - NullPointerException in Svn2Scanner
Resolution
FE-4687 - NullPointerException in Svn2Scanner is marked to be fixed in Fisheye / Crucible 3.0.2 release.
Was this helpful?