[
https://issues.apache.org/jira/browse/KARAF-7264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450861#comment-17450861
]
ASF subversion and git services commented on KARAF-7264:
--------------------------------------------------------
Commit 8eb0c585a27b7260886591b6433f0ad1fe33d7ac in karaf's branch
refs/heads/karaf-4.2.x from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=8eb0c58 ]
[KARAF-7264] Graceful (not immediate) shutdown shell command session
(cherry picked from commit 80ae4361a91a60b49b71b5e4c8b8aafb1124670a)
> SSH Session closed immediately suppresses response to Client
> ------------------------------------------------------------
>
> Key: KARAF-7264
> URL: https://issues.apache.org/jira/browse/KARAF-7264
> Project: Karaf
> Issue Type: Improvement
> Components: karaf
> Affects Versions: 4.3.3
> Reporter: Rico Neubauer
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> As discussed in channel:
>
> we're encountering an issue with latest 4.3.3, which seems to be caused by
> this change: [KARAF-7190]
> [https://github.com/apache/karaf/pull/1427/commits/8cc2b247d0ae8b2c95439cf5a45118b8f0eb3b47]
> When connecting via SSH (Apache Mina client in our case), we expect a return
> code for some of the commands we issue. The code still sends back the
> command, but then invokes close with parameter immediate=true. This leads to
> the return code almost never arriving at calling client.
> If changed to session.close(false), the buffers get flushed and we retrieve
> the return code again.
>
> Not sure about the close in factory#destroy - there immediate=true might be ok
>
> Can provide a PR, if liked - please let me know whether with or without the
> #close in #destroy
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
