'Process timed out' when Connecting to a Perforce Repository
症状
Fisheye fails to connect to the Perforce repository and reports following error in the logs:
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:
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 infoさらなるトラブルシューティング
Try running the above command directly via the command line:
C:\Program Files\Perforce\p4v.exe -p <Server Address> -ztag infoand check if you get the correct result.
原因
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.
ソリューション
Update the p4 executable filename to help resolve the problem.
最終更新日 2018 年 11 月 2 日
Powered by Confluence and Scroll Viewport.