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

Piotr Klimczak updated KARAF-7839:
----------------------------------
    Description: 
Karaf client idle timeout doesn't work if longer than 60s (heart beat).

This can be reproduced by:
 # Downloading vanilla karaf
 # Changing idle timeout in "org.apache.karaf.shell.cfg" to "sshIdleTimeout = 
90000"
 # Start karaf with ./bin/karaf
 # Start client in separate terminal with ./bin/client

Suspicion is that the bug was introduced here: 
https://issues.apache.org/jira/browse/KARAF-7051

Last tested and working version for me was 4.3.1. Not tested any other 4.3 
versions.

  was:
Karaf client idle timeout doesn't work if longer than 60s (heart beat).

This can be reproduced by:
 # Downloading vanilla karaf
 # Changing idle timeout in "org.apache.karaf.shell.cfg" to "sshIdleTimeout = 
90000"
 # Start karaf with ./bin/karaf
 # Start client in separate terminal with ./bin/client

Suspicion is that the bug was introduced here: 
https://issues.apache.org/jira/browse/KARAF-7051

Last tested and working version for me was 4.3.1.


> Karaf client ssh idleTimeout not working
> ----------------------------------------
>
>                 Key: KARAF-7839
>                 URL: https://issues.apache.org/jira/browse/KARAF-7839
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.4.3, 4.4.6
>            Reporter: Piotr Klimczak
>            Priority: Minor
>
> Karaf client idle timeout doesn't work if longer than 60s (heart beat).
> This can be reproduced by:
>  # Downloading vanilla karaf
>  # Changing idle timeout in "org.apache.karaf.shell.cfg" to "sshIdleTimeout = 
> 90000"
>  # Start karaf with ./bin/karaf
>  # Start client in separate terminal with ./bin/client
> Suspicion is that the bug was introduced here: 
> https://issues.apache.org/jira/browse/KARAF-7051
> Last tested and working version for me was 4.3.1. Not tested any other 4.3 
> versions.



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

Reply via email to