Response is never received when the command output is too big
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 620
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 11
Description
Using version 0.27.0.
I'm using sshj for testing purposes, executing commands on a remote server. I've found an issue that I believe is serious. Here's my scenario:
1. Login to a remote host
2. Build a command and execute it with
`cmd = session.exec(runJarCmd.toString());
cmd.join();`
3. The command launches a java application (java -jar ..) which produces a very big output (2-2.5mb)
4. Due to the big output size, the command never exits and my app (not the remote java app) freezes forever although the remote java app has finished long time ago. There are no exceptions or anything ... it just freezes forever (or until my timeout is reached, but I've set it to 24 hours ...)
I've verified this by redirecting the command output to a file like "java -jar .. > mylog.log". If I send the command like this, everything passes just fine and my code does not get stuck.
If I can provide more details please let me know.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.