It seems that the channel close causes the session to close as well.
I will see if I can work up a simple, short, contained example and open a
defect.
Claude
On Thu, Nov 17, 2016 at 9:23 PM, Guillaume Nodet wrote:
> It's a valid use case and it should work.
>
> However, if you stack your sessi
It's a valid use case and it should work.
However, if you stack your sessions for too long, the client or server may
consider the session idle for too long and close it.
Before reusing the session, check the session state with a call isOpen().
You can change the timeout on the client or server (if
I am attempting to create a client session and then use it to send multiple
commands. Is this possible?
{noformat}
ConnectFuture connect = client.connect(cred.getUserName(),
socketAddress);
if (connect.await(1)) {
session = connect.g
