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

Craig commented on KARAF-7174:
------------------------------

I ran into this and it seems that when you leave the log:tail running and it 
hits the timeout, I am kicked back out to the shell prompt, and if I try to 
login again I can't get back into the client.  Additionally, if I use the OS 
level tail of the actual karaf.log file it seems like it isn't processing 
anything either and it is completely hung.  The only answer is to restart karaf 
completely.  This seems like a major issue.  I see that it has been around 
since 2021, is there a plan to address this?

> log:tail threads keep running after ssh exits
> ---------------------------------------------
>
>                 Key: KARAF-7174
>                 URL: https://issues.apache.org/jira/browse/KARAF-7174
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.3.2
>         Environment: Ubuntu 20.04.2 LTS
> Clean out-of-the-box Karaf 4.3.2 distribution
>            Reporter: Gabriel Andrade
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>         Attachments: log-tail stack trace.txt
>
>
> When executing log:tail via Karaf's ssh connection, the created thread is not 
> killed when the ssh connection is killed or timeouts.
> I believe that all threads launched via ssh should be killed if the session 
> is no longer active.
> Steps to reproduce:
>  * Open a ssh connection with Karaf
>  * {{Run log:tail}}
>  * Either close the session without exiting log:tail or wait until it 
> timeouts in a few minutes;
>  * {{Run shell:threads | grep log:tail on the console or another ssh 
> connection}}
>  * A log tail thread should still be running.
> Every time this process is repeated, a new log:tail thread will appear and 
> stay alive.
> I've attached the return of one of my shell:thread commands.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to