Hopefully this comment appears under Eddie Webb’s comment. There’s no link to comment on a comment.
Addressing your comment back to front:
I don’t know if something is seriously wrong. I do know that it’s a very big repository. Before I used the hundreds of exclude patterns, I kept getting errors like
2013-04-07 02:16:02,769 ERROR [InitialPinger1 try11] fisheye BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo try11 due to class java.lang.OutOfMemoryError -
Java heap space
java.lang.OutOfMemoryError: Java heap space
which would abort the initial import. I used FISHEYE_OPTS to gradually increase the Java heap, eventually getting to “-Xmx12288m” before I gave up. I logged all the perforce commands, and I could tell that it got further and further into the repository as I increased the memory.
With the exclude patterns, though, I have FISHEYE_OPTS set to “-Xmx4096m” and things go fine until I get the java.util.ConcurrentModificationException.
As to the number of threads I use for initial scan: I never set it. I assume it was whatever the default was. I just checked http://localhost:8060/admin/viewServerSettings.do and it said under Resource Limits that Initial Indexing Threads was not set and Incremental Indexing Threads was not set. I just changed them both to 1 and restarted the server. It’s trying to do the initial import again. We can see what happens in another 8 hours or so.
Some other data from http://localhost:8060/admin/sysinfo.do :
Resource Limits - initial threads: 1 (max)
Resource Limits - incremental threads: 1 (max)
Database Type: MySQL
Database Driver: com.mysql.jdbc.Driver
Database Url: jdbc:mysql://localhost:3306/fisheye
Database Version: 80
JDBC Pool (min): 5
JDBC Pool (max): 20
JDBC Pool (effective max): 18
JDBC Pool (partitions): 3
JDBC Pool (max per partition): 6
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.