[
https://jira.codehaus.org/browse/WAGON-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Tran updated WAGON-431:
---------------------------
Description:
When the remote execution has stdout output > 32K ( hardcoded by jsch)
CommandExecutorStreamProcessor hangs waiting for remote stderr end of stream
which never arrive since remote shell is blocked by 32 buffer filled by stdout
The solution is process stdout first ( instead of stderror), however we may
encounter the same issue if stderr output is more than 32K which less likely
the happen then stdout
My be better to use StreamPumper from PlexusUtils to prevent blocking
was:
When the remote execution has stdout output > 32K ( hardcoded by jsch)
CommandExecutorStreamProcessor hangs waiting for remote stderr end of stream
which never arrive since remote shell is blocked by 32 buffer filled by stdout
The solution is process stdout first ( instead of stderror), however we may
encounter the same issue if stderr output is more than 32K which less likely
the happen then stdout
> wagon ssh exec's hangs stdout output > 32K
> -------------------------------------------
>
> Key: WAGON-431
> URL: https://jira.codehaus.org/browse/WAGON-431
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Affects Versions: 2.4, 2.5, 2.6, 2.7, 2.8
> Reporter: Dan Tran
> Assignee: Dan Tran
>
> When the remote execution has stdout output > 32K ( hardcoded by jsch)
> CommandExecutorStreamProcessor hangs waiting for remote stderr end of stream
> which never arrive since remote shell is blocked by 32 buffer filled by stdout
> The solution is process stdout first ( instead of stderror), however we may
> encounter the same issue if stderr output is more than 32K which less likely
> the happen then stdout
> My be better to use StreamPumper from PlexusUtils to prevent blocking
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
