You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2016/08/30 05:49:20 UTC

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

     [ https://issues.apache.org/jira/browse/KARAF-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang resolved KARAF-4682.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 4.1.0

> 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
>             Fix For: 4.1.0
>
>
> 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)