Details
-
Bug
-
Resolution: Answered
-
Low
-
None
-
None
-
Severity 3 - Minor
-
Description
These exceptions have been reported in a support case:
[snip] 2012-06-25 03:30:43,856 DEBUG [main ] fisheye.app P4Exec-getProcessStatusMessage - Exception processing P4 command - returning as status com.atlassian.utils.process.ProcessException: Non-zero exit code: 1 at com.atlassian.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:83) [snip]
(new in 2.7.14, not seen on 2.7.10)
and
fisheye.app P4Exec-getProcessStatusMessage - Exception processing P4 command - returning as status com.atlassian.utils.process.ProcessException: Non-zero exit code: 1 at com.atlassian.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:83) at com.atlassian.utils.process.ExternalProcessImpl.finish(ExternalProcessImpl.java:308) at com.atlassian.utils.process.ExternalProcessImpl.execute(ExternalProcessImpl.java:351) at com.cenqua.fisheye.perforce.client.P4Exec.login(P4Exec.java:131)
(Seen since at least 2.7.7)
Investigate if these error messages are spurious over-reporting that occur as part of normal perforce operation (most likely) or if they potentially indicate a problem. If they are spurious, determine if we can catch the specific exception and just log a message saying what perforce said and what it means, rather than a full stack trace,