Mule Cloud Connector
| com.trilead.ssh2.ChannelCondition |
Contains constants that can be used to specify what conditions to wait for on
a SSH-2 channel (e.g., represented by a Session).
| Constants | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| int | CLOSED | The underlying SSH-2 channel, however not necessarily the whole connection, has been closed. | |||||||||
| int | EOF | EOF on has been reached, no more _new_ stdout or stderr data will arrive from the remote server. | |||||||||
| int | EXIT_SIGNAL | The exit signal of the remote process is available. | |||||||||
| int | EXIT_STATUS | The exit status of the remote process is available. | |||||||||
| int | STDERR_DATA | There is stderr data available that is ready to be consumed. | |||||||||
| int | STDOUT_DATA | There is stdout data available that is ready to be consumed. | |||||||||
| int | TIMEOUT | A timeout has occurred, none of your requested conditions is fulfilled. | |||||||||
The underlying SSH-2 channel, however not necessarily the whole connection,
has been closed. This implies EOF. Note that there may still
be unread stdout or stderr data in the local window, i.e, STDOUT_DATA
or/and STDERR_DATA may be set at the same time.
EOF on has been reached, no more _new_ stdout or stderr data will arrive
from the remote server. However, there may be unread stdout or stderr
data, i.e, STDOUT_DATA or/and STDERR_DATA
may be set at the same time.
The exit signal of the remote process is available.
The exit status of the remote process is available. Some servers never send the exist status, or occasionally "forget" to do so.
There is stderr data available that is ready to be consumed.
There is stdout data available that is ready to be consumed.
A timeout has occurred, none of your requested conditions is fulfilled.
However, other conditions may be true - therefore, NEVER use the "=="
operator to test for this (or any other) condition. Always use
something like ((cond & ChannelCondition.CLOSED) != 0).