Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.1.0
-
Component/s: None
-
Labels:None
Description
I saw ConsoleSessionImpl thread running indefinitely in itests if the test crash, this just leave many dead jvm process.
This is caused by while (running) loop never exit in ConsoleSessionImpl if somehow the container crash.
This line
command = reader.readLine(getPrompt());
the command is null when this error happen but ConsoleSessionImpl.close() never get invoked because other thread which is suppose to call ConsoleSessionImpl.close() just dead, we should break the loop when detect command is null.