[
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 (default for 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 is from test client:
{code:java}
karaf@root()> date
Jun Mon 17 14:41:50 2024
karaf@root()> date
Jun Mon 17 14:50:08 2024
karaf@root(config)> config:list | grep ssh
ssh = org.apache.karaf.shell.ssh
featuresBoot = instance/4.4.6, package/4.4.6, log/4.4.6, ssh/4.4.6,
framework/4.4.6, system/4.4.6, eventadmin/4.4.6, feature/4.4.6, shell/4.4.6,
management/4.4.6, service/4.4.6, jaas/4.4.6, deployer/4.4.6, diagnostic/4.4.6,
wrap/2.6.14, bundle/4.4.6, config/4.4.6, kar/4.4.6
sshHost = 0.0.0.0
sshIdleTimeout = 90000
sshPort = 8101
sshRealm = karaf
sshRole = ssh
log4j2.logger.sshd.level = INFO
log4j2.logger.sshd.name = org.apache.sshd
feature.ssh = ssh
{code}
client should have timed out before 2nd date command, but it didn't.
We only noticed that because our containers started running out of memory and
it was caused by many "client" instances open within container.
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. Not tested any other 4.3
versions.
This is from test client:
{code:java}
karaf@root()> date
Jun Mon 17 14:41:50 2024
karaf@root()> date
Jun Mon 17 14:50:08 2024
karaf@root(config)> config:list | grep ssh
ssh = org.apache.karaf.shell.ssh
featuresBoot = instance/4.4.6, package/4.4.6, log/4.4.6, ssh/4.4.6,
framework/4.4.6, system/4.4.6, eventadmin/4.4.6, feature/4.4.6, shell/4.4.6,
management/4.4.6, service/4.4.6, jaas/4.4.6, deployer/4.4.6, diagnostic/4.4.6,
wrap/2.6.14, bundle/4.4.6, config/4.4.6, kar/4.4.6
sshHost = 0.0.0.0
sshIdleTimeout = 90000
sshPort = 8101
sshRealm = karaf
sshRole = ssh
log4j2.logger.sshd.level = INFO
log4j2.logger.sshd.name = org.apache.sshd
feature.ssh = ssh
{code}
client should have timed out before 2nd date command, but it didn't.
We only noticed that because our containers started running out of memory and
it was caused by many "client" instances open within container.
> 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 (default for 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 is from test client:
> {code:java}
> karaf@root()> date
> Jun Mon 17 14:41:50 2024
> karaf@root()> date
> Jun Mon 17 14:50:08 2024
> karaf@root(config)> config:list | grep ssh
>
>
> ssh = org.apache.karaf.shell.ssh
> featuresBoot = instance/4.4.6, package/4.4.6, log/4.4.6, ssh/4.4.6,
> framework/4.4.6, system/4.4.6, eventadmin/4.4.6, feature/4.4.6, shell/4.4.6,
> management/4.4.6, service/4.4.6, jaas/4.4.6, deployer/4.4.6,
> diagnostic/4.4.6, wrap/2.6.14, bundle/4.4.6, config/4.4.6, kar/4.4.6
> sshHost = 0.0.0.0
> sshIdleTimeout = 90000
> sshPort = 8101
> sshRealm = karaf
> sshRole = ssh
> log4j2.logger.sshd.level = INFO
> log4j2.logger.sshd.name = org.apache.sshd
> feature.ssh = ssh
> {code}
> client should have timed out before 2nd date command, but it didn't.
> We only noticed that because our containers started running out of memory and
> it was caused by many "client" instances open within container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
