'Process timed out' when Connecting to a Perforce Repository
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
Fisheye fails to connect to the Perforce repository and reports following error in the logs:
1
2
3
4
5
6
7
8
9
10
11
2012-12-05 13:17:13,390 ERROR [btpool0-23 <Repo_Name>] fisheye RepositoryAdminRpcServiceImpl-testRepositoryConnection - Error testing connection.
com.atlassian.fisheye.spi.admin.services.RepositoryConfigException: com.cenqua.fisheye.config.ConfigException: Problem communicating with repository : Unable to get repository info: com.atlassian.utils.process.ProcessTimeoutException:process timed out
at com.atlassian.fisheye.spi.admin.impl.DefaultRepositoryAdminService.testConnectionFor(DefaultRepositoryAdminService.java:540)
Caused by: com.cenqua.fisheye.config.ConfigException: Problem communicating with repository : Unable to get repository info: com.atlassian.utils.process.ProcessTimeoutException:process timed out
Caused by: com.cenqua.fisheye.perforce.client.P4ClientException: Unable to get repository info: com.atlassian.utils.process.ProcessTimeoutException:process timed out
at com.cenqua.fisheye.perforce.client.P4Client.info(P4Client.java:83)
at com.cenqua.fisheye.perforce.P4ScmConfig.testConnection(P4ScmConfig.java:151)
... 129 more
2012-12-05 13:17:13,515 ERROR [btpool0-23 <Repo_Name>] fisheye RepositoryAdminRpcServiceImpl-testRepositoryConnection - Connection failed.
fisheye-debug-<date>.log reports:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
2012-12-05 18:18:36,694 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4EDITOR = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4MERGE = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4CHARSET = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4PAGER = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - PWD = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - TMP = C:\WINDOWS\TEMP
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - TEMP = C:\WINDOWS\TEMP
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4TICKETS = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4LANGUAGE = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4COMMANDCHARSET = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4DIFFUNICODE = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4MERGEUNICODE = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4AUDIT = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4JOURNAL = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4LOG = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4PORT = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4ROOT = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4DEBUG = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4NAME = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4DESCRIPTION = null
2012-12-05 18:18:36,709 DEBUG [btpool0-2 ection-1354760316631] fisheye P4Exec-dumpP4Env - P4ZEROCONF = null
2012-12-05 18:18:36,725 DEBUG [btpool0-2 ection-1354760316631] fisheye P4CliUtils-dumpCommandLine - [<URL>] Executing C:\Program Files\Perforce\p4v.exe -p <Server Address> -ztag infoFurther Troubleshooting
Try running the above command directly via the command line:
1
C:\Program Files\Perforce\p4v.exe -p <Server Address> -ztag infoand check if you get the correct result.
Cause
Fisheye is not configured correctly to point to the right p4 executable. In this case, Fisheye is using the incorrect p4v.exe file instead of the expected p4.exe executable.
Resolution
Update the p4 executable filename to help resolve the problem.
Was this helpful?