tomaswolf commented on issue #403: URL: https://github.com/apache/mina-sshd/issues/403#issuecomment-1680179319
Related: - https://community.progress.com/s/question/0D54Q00009gkVdYSAU/wsftp126-fails-to-transfer-large-file-to-sftp-server-from-apache - https://community.progress.com/s/question/0D54Q0000ASQm9FSQT/bad-length-32796-for-cmdsshmsgchanneldata-max-allowed32768 reported in 2022 for WS_FTP 12.6, and in 2023 for 12.7 and 12.8. Seems to be specific to WS_FTP, which I don't have. @dragonknight88 : if you can run the Apache MINA sshd server with trace logging, it should dump buffer contents. Hopefully it also does so when this exception occurs. (Or if you can live debug the server, a breakpoint where that exception is raised in [`AbstractChannel.validateIncomingDataSize()`](https://github.com/apache/mina-sshd/blob/786fd51ba20e0dc1ed998a6fe3772156983e18a9/sshd-core/src/main/java/org/apache/sshd/common/channel/AbstractChannel.java#L857) should let you examine the buffer contents.) Then we could look at what the actual bytes of this message are. Perhaps that gives a clue. (I'd also be interested to know what the total length of that buffer is at that point -- i.e., its number of available bytes.) Also, it would be interesting to know when exactly it occurs. What messages were exchanged over the channel already when the exception occurs? A debug log of the server would help. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
