You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/01/22 12:59:39 UTC

[jira] [Commented] (JCLOUDS-1053) jclouds-sshj doesn't handle getExitStatus returning null

    [ https://issues.apache.org/jira/browse/JCLOUDS-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112343#comment-15112343 ] 

ASF subversion and git services commented on JCLOUDS-1053:
----------------------------------------------------------

Commit a4b8a73790d057498cd7f88e936e870a61c1c98e in jclouds's branch refs/heads/master from [~devcsrj]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=a4b8a73 ]

JCLOUDS-1053: Fallback to -1 when sshj exit status returns null


> jclouds-sshj doesn't handle getExitStatus returning null
> --------------------------------------------------------
>
>                 Key: JCLOUDS-1053
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1053
>             Project: jclouds
>          Issue Type: Bug
>            Reporter: Michael Wilson
>
> In the SshjSshClient ExecConnection.create function, this line:
> {noformat}
>             int errorStatus = output.getExitStatus();
> {noformat}
> Does not currently handle the case when output.getExitStatus() is null, which is a valid return value according to SSHJ's JavaDocs. It's possible that the command needs to be explicitly closed before calling getExitStatus: https://github.com/hierynomus/sshj/issues/114.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)