[jira] [Commented] (KARAF-4682) avoid ConsoleSessionImpl thread running indefinitely

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on KARAF-4682:
--------------------------------------------------------

Commit d3eaedcf1cf43c5d06f16607631b3704716683bc in karaf's branch refs/heads/master from [~ffang]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=d3eaedc ]

[KARAF-4682]avoid ConsoleSessionImpl thread running indefinitely


> avoid ConsoleSessionImpl thread running indefinitely 
> -----------------------------------------------------
>
>                 Key: KARAF-4682
>                 URL: https://issues.apache.org/jira/browse/KARAF-4682
>             Project: Karaf
>          Issue Type: Bug
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>
> 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
> {code}
> command = reader.readLine(getPrompt());
> {code}
> 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. 



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